Hello, I'm looking for an efficient way to synchronize geometry updates, that is, I have some geometries that I want to update, but I would like that the user doesn't see an update after the other, but only sees the final result.
I have tried to stop the rendering through universe.getCanvas().stopRenderer(), to achieve my geometry update and to start the rendering again with startRenderer(), but it seems that Java3D handles the geometry updates requests (that I do through Shape3D.setGeometry() since it is in my examples much faster to rebuild the geometry each time than to update the vertex' coordinates with the capability ALLOW_COORDINATES_WRITE enabled - would geometry by reference be faster by the way?) asynchronously. Do you see a way to avoid those ugly progressive geometry updates? Something like a transaction that you build (the various updates) and finally commit? Mmmh, might have done too much database programming... Thanks for any hint or suggestion! Roland =========================================================================== 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".
