Fred Klingener wrote: > I think that's overstating it a bit. If I understand Sun's > guidance on this, you are guaranteed two things: 1.) that the > rendering thread will wait for you to finish with your > processStimulus(), and 2.) no other processStimulus() will start > or run until you exit.
That is not a correct assumption. Nominally all behaviours can run in parallel. For example collision detection behaviours run in parallel to the elapsedFrame behaviours and AWT stuff. Now, given that most people use single CPU machines, then the above is a reasonable assumption, but not necessarily correct. -- Justin Couch http://www.vlc.com.au/~justin/ Freelance Java Consultant http://www.yumetech.com/ Author, Java 3D FAQ Maintainer http://www.j3d.org/ ------------------------------------------------------------------- "Humanism is dead. Animals think, feel; so do machines now. Neither man nor woman is the measure of all things. Every organism processes data according to its domain, its environment; you, with all your brains, would be useless in a mouse's universe..." - Greg Bear, Slant ------------------------------------------------------------------- =========================================================================== 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".
