[x3d-public] Requirement for v4. one X3D element per Frame

John Carlson yottzumm at gmail.com
Thu Jan 31 21:42:37 PST 2019


Don’t spend too much time thinking about this. Find a reason not to support this or to support this.  It doesn’t make too much difference to me.   My mind is already thinking about workarounds for my code (returning an autogenerated id from loadScripts perhaps).  At least I managed to stimulate my brain into thinking for a while.

>>Can we autogenerate an incrementing browser # and stick it into the outer scenegraph as a div id?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190131/7db1c3ba/attachment.html>


More information about the x3d-public mailing list