> Date: Mon, 24 Feb 2003 13:17:45 -0500 > From: Hong <[EMAIL PROTECTED]> > > GeometryUpdaterHi, > =20 > IMHO, GeometryUpdater provide a way to allow user to update the > geometry dynamically and efficiently by the following reasons: > 1. Thread safe. (Java3D is rendering on its own thread). > 2. Efficiency. I believe that attach/detach a live scene on the = > BranchGroup > is relatively slow. If the Geometry object you are trying to = > update is=20 > under a big BranchGroup, the overhead would be even bigger! > 3. ... > > There might be other reasons that people can provide in this group. > There is a sample program in Java3DTutorial/animation that = > demonstrates > how to use GeometryUpdater. You might want to check it out.
The only reason to use GeometryUpdater is that it is required for by-reference usage of GeometryArray. In by-copy mode, Java 3D copies the vertex data that you provide and can thus synchronize the update with its internal data structures. In by-reference mode you are directly modifying the arrays to which your references point -- this has to be synchronized with the other threads contending for access to the data. The GeometryUpdater interface is what you implement to allow Java 3D to perform this synchronization. -- Mark Hood =========================================================================== 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".
