search

x3dom / x3dom

X3DOM. A framework for integrating and manipulating X3D scenes as HTML5/DOM elements.
http://x3dom.org
Other
815 stars 271 forks source link

update cycleInterval change behavior #1289

Closed andreasplesch closed 10 months ago

andreasplesch commented 10 months ago

X3D v.4 no longer ignores changes to cycleInterval of an active Timesensor. fraction is now recalculated, or the sensor stopped.

andreasplesch commented 10 months ago

https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/time.html#TimeSensor

but

https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/time.html#TimeSensor

does not have the change.

brutzman commented 10 months ago

Thanks for careful checking of this important original recommendation. Here is further document checking to illustrate our due-diligence process for resolving specification issues.

I believe that you will find the highlighted sentences in the "final proof" version, endorsed by Web3D Consortium and sent to ISO editors (still awaiting their final-final publication as an ISO/IEC standard), online as follows, and maintained in GitHub.

and (accessible to Web3D Consortium members)

Backtracking, looking at the CD1 version of same file shows HTML-source edits applied with markup <span class="proposed" title="Mantis 1080"> which refers to Mantis issue tracker. Mantis entries contain distilled summaries of key public discussions, X3D Working Group meetings, and X3D4 ISO Editor discussions by Dick Puk and myself (accessible to Web3D Consortium members) at

Again, thanks for your notification of a potential issue and seeking clarity while implementing. It is exactly this kind of careful checking, backed up by implementation and evaluation of examples, that makes the X3D4 Graphics Specification such a powerful document.

Very respectfully yours.

brutzman commented 10 months ago

PDF of Mantis issue 1080 attached showing example detailed scrutiny. Yes, this approach takes a long time to work through, but the power of community effort (stretching back to 1994 origins of VRML97 ISO Standard) are undeniable. Changes might have one person committing/clicking but no change is applied to specification itself without consensus, confirmed by at least 2 people on the spot agreeing that consistency and consensus have been achieved. Mantis1080TimeSensorChanges.pdf

Onward we go. All of us are smarter together than any of us. Again thanks for superlative efforts of X3DOM team.

andreasplesch commented 10 months ago

Thanks for the clarification. Responding immediately to cycleInterval changes will be welcomed by users. For implementers it is critical to have a focused test example.

The Mantis record points to

https://web3d.org/pipermail/x3d-public_web3d.org/2016-November/thread.html#start

for discussion on the change.

andreasplesch commented 10 months ago

1291 now implements the change.