[x3d-public] dynamic cycleInterval changes
patrick.daehne at igd.fraunhofer.de
Mon Nov 21 06:48:20 PST 2016
time.enabled = false;
time.cycleInterval = 5;
time.enabled = true;
… Events generated by setting an input-capable field on a node are sent at the completion of the initial function call made to the user code by the browser. … Assigning to the inputOnly field multiple times during one execution of the function still only sends one event and that event shall be the last value assigned.
So in X3D conformant browsers, the lines above send only two events:
1. time.enabled = true
2. time.cycleInterval = 5
The first assignment to time.enabled gets overwritten by the second assignment, so the timer never gets disabled.
> Am 20.11.2016 um 21:36 schrieb Andreas Plesch <andreasplesch at gmail.com>:
> I want to change the cycleTime of a TimeSensor in a x3d script:
> cycleTime input events are ignored when the TimeSensor is enabled. So it is necessary to disable it first, then change the cycleTime and then reenable it.
> However, in all tested browser the above does not work as expected. These are cobweb, instant player and bs contact. bs contact also has this console message:
> Script node speeder: parse error: line 16 "time.cycleInterval = 2;" ()
> and therefore does not get to change the color to grey.
> cobweb and instant player change the color but do not slow down the ball.
> I first thought that cobweb does not correctly work through the sequence of events but since no browser works sofar I start to think that I am missing something.
> Any help or feedback appreciated,
More information about the x3d-public