Has anyone had any issues with v1.2.1 relating to random branch groups not
getting rendered? Our app is definitely acting differently under v1.2.1
than under beta 2. This may be showing up a bug in our code and I have a
lot more testing to do before I can figure out what is happening.
Specifically I was wondering if there were any changes to behavior
scheduling or changes made to the re-entrancy of Java3d objects being
updated from threads. As a particular example I have a piece of geometry
which has always been at a particular location, but which is no longer
there. I can see where the geometry is getting constructed and then being
added to a transaction. The transaction is queued and processed by a
behavior. If there is a bug in our code it is somewhere in the transaction
processing. Maybe something has changed in the timing that is causing a bug
in our code to drop transaction nodes on the floor.
Anyway, I will continue debugging.
Dave Yazel
===========================================================================
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".
