[x3d-public] [...] HAnim2 X3D4 BoxMan update: does ClassicVRML Grammar allows ROUTE in children?
Patrick Dähne
pdaehne at gmail.com
Thu Jan 5 11:04:38 PST 2023
Hello,
I did not want to start a big discussion here, I just wanted to explain why the given „BoxManJoeAnim.reworked.x3dv“ might not import correctly because the ROUTEs are inside an MFNode field which - according to the grammar - is not allowed. Below are three simple examples, the first two are valid, the third is invalid. „BoxManJoeAnim.reworked.x3dv“ corresponds to the third example.
Bye,
Patrick
—
Example 1 (valid, ROUTE at top level):
Relevant grammar rules: x3dScene -> statements -> statement -> routeStatement
###
Group {
children [
DEF ts TimeSensor { … }
DEF oi OrientationInterpolator { … }
]
}
ROUTE ts.fraction_changed TO oi.set_fraction
###
—
Example 2 (valid, ROUTE in node body):
Relevant grammar rules: x3dScene -> statements -> statement -> nodeStatement -> node -> nodeBody -> nodeBodyElement -> routeStatement
###
Group {
children [
DEF ts TimeSensor { … }
DEF oi OrientationInterpolator { … }
]
ROUTE ts.fraction_changed TO oi.set_fraction
}
###
—
Example 3 (*invalid*, ROUTE in MFNode field):
Relevant grammar rules: x3dScene -> statements -> statement -> nodeStatement -> node -> nodeBody -> nodeBodyElement -> fieldValue -> mfnodeValue -> nodeStatements -> nodeStatement -> ???
###
Group {
children [
DEF ts TimeSensor { … }
DEF oi OrientationInterpolator { … }
ROUTE ts.fraction_changed TO oi.set_fraction
]
}
###
More information about the x3d-public
mailing list