[x3d-public] dynamic cycleInterval changes
brutzman at nps.edu
Fri Nov 25 12:24:24 PST 2016
Here is the specification comment I submitted regarding this issue. Improvements welcome.
Comment on 19775-1: Abstract X3D Definitions - V3.3
Issue: TimeSensor cycleInterval needs to be modifiable when running
It is not feasible to modify TimeSensor cycleInterval without major
machinations and likely failure.
"An active TimeSensor node ignores set_cycleInterval and set_startTime
events. An active TimeSensor node also ignores set_stopTime events for
set_stopTime less than or equal to startTime."
Email discussion illustrates difficulties with modifying cycleInterval
Subject: dynamic cycleInterval changes
Issues such as event-arrival nondeterminism, usability and HTML5/DOM
interoperability are all interrelated on this topic.
Best place to fix this is in TimeSensor algorithm/code itself. Necessary
change is to make TimeSensor cycleInterval modifiable when running in order
to avoid two-phase commits and a host of other difficulties.
all the best, Don
Don Brutzman Naval Postgraduate School, Code USW/Br brutzman at nps.edu
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
More information about the x3d-public