[x3d-public] TimeSensor resumeTime field [Mantis 1106]

[Yves Piguet]

A global pause is more practical for pausing the whole scene, because otherwise you have to route a pause event to all time-related nodes (TimeSensor, other nodes enumerated in 19775 8.2.4.1 http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/time.html#TimeDependentNodesOverview and nodes related to physics models)

Pausing correctly is important especially on mobile devices where the user wants to reduce power consumption without quitting the browser.

I haven't found pause/resume methods in 19775-2  (SAI). I'd suggest to add this functionality there.

Yves

> On 19 Dec 2016, at 17:36, Andreas Plesch <andreasplesch at gmail.com> wrote:
> 
> Thanks Roy,
> 
> the next step may be to come up with a simple test scene (as I could not find any in the x3d examples collection) and check how different x3d browsers behave.
> 
> A directly related question is how x3d/vrml scenes managed pausing of animations before pause/resumeTime was introduced ? If there is a well known strategy/method for pausing, this issue may become almost irrelevant. But it seems pausing would involve stopping, and then restarting with a startTime at the appropriate time in the past:
> 
> timeOffset = fraction_changed_whenStopped * cycleInterval
> startTime = now - timeOffset
> 
> Setting startTime of an inactive sensor to a time in the past seems to be allowed.
> 
> This looks like it would require scripting, and does make a built in pausing functionality more attractive.
> 
> -Andreas