Difference between revisions of "ViewpointInlineMain.x3d"

From Web3D.org
Jump to: navigation, search
(acknowledge Flux)
 
Line 46: Line 46:
 
| Not Expected  
 
| Not Expected  
 
| Sets initial viewpoint to inline bindable
 
| Sets initial viewpoint to inline bindable
|  
+
|-
 +
| Flux
 +
| Latest(28/05/2007)
 +
| Expected
 +
|
 
|-
 
|-
 
| Vivaty
 
| Vivaty

Latest revision as of 12:08, 11 September 2011

Tests initial binding of viewpoints with Inlined content. Should be at 0 0 10. Some browsers are allowing Inlined content to be the first available binding node.


<?xml version="1.0" encoding="UTF-8"?>
<X3D profile="Interactive">
  <Scene>
      <Shape><Box /></Shape>
      <Inline url="ViewpointInline.x3d" />
  </Scene>
</X3D>
<?xml version="1.0" encoding="UTF-8"?>
<X3D profile="Interchange">
  <Scene>
    <Viewpoint description="Inlined" position="0 0 5" />
  </Scene>

Browser Results

Browser Version Result Notes
BS Contact 7.107 Expected
FreeWRL Untested
Octaga 2.2.0.12 Expected
Instant Reality 2.0.0_beta4 Not Expected Sets initial viewpoint to inline bindable
Flux Latest(28/05/2007) Expected
Vivaty Latest(7/28/2008) Expected
Xj3D 2_M1_DEV_2008-06_02 Expected

Specification Notes

From 7.2.2:

During read, the first encountered <bindable node> in each layer is bound by pushing it to the top of the <bindable node> stack for that layer. Nodes contained within files referenced by Inline nodes, within the strings passed to the Browser.createX3DFromString() method, or within X3D files passed to the Browser.createX3DFromURL() method (see Part 2 of ISO/IEC 19775) are not candidates for the first encountered <bindable node>. The first node within a locally defined prototype instance is a valid candidate for the first encountered <bindable node>. The first encountered <bindable node> sends an isBound TRUE event.

So the default values of 0 0 10 should be used, not 0 0 5 from the Inline.