> From: Bruno Feurer <[EMAIL PROTECTED]>
>
> I would like to implement a direct event handling with Java3D. Some nodes
> should implement a listener interface and should be registered at some
> objects of the problem domain. So if the problem domain changes, the Java3D
> scene reacts directly (and not over behavior event-dispatching).
>
> Because the problem domain is active and changes the scene independent from
> the rendering thread, the Java3D should be thread safe. Is it? I've read the
> mail from Andrei Cioroianu
> (http://archives.java.sun.com/cgi-bin/wa?A2=ind9811&L=java3d-interest&D=0&P=
> 852), but I have not found an answer yet.
This should work fine. Scene graph changes can be made from any thread.
Making changes from a behavior has the advantage that all the changes made in a
behavior callback will appear the same frame. Other than that, there is no
advantage or disadvantage to making scene graph changes from any particular
thread.
Doug Gehringer
Sun Microsystems
===========================================================================
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".
