Fergus Murray wrote:
> >Updating one object in real time is too much for the EAI. The basic
> >problem is that you have events coming from outside of the runtime scope
> >of the scene graph.
>
> Isn't this just the same as what you get with a Script node? Or does the
> fact that it's got its own node mean that it slyly avoids this problem?
>
You can think of a script node as a small piece of code sandwiched
between routes. It flows smoothly inside the standard event model of
VRML. So there is no question about when a piece of script code's
events are processed.
Same rule as J3D behaviours, do not do any long calculations inside a
script. If you are accessing a network connection then you will need to
have that handled on a seperate thread to avoid slowing the rendering.
--
Alan Hudson
President: Yumetech, Inc. http://www.yumetech.com/
Web3D Open Source Chair http://www.web3d.org/TaskGroups/source/
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
