Hi Fred: Thanks again for detailing your approach.
A behavior that implements ActionListener....very imaginative I should say. Now I know what you meant by doing everything thru' a processStimulus. Will try that once I read up and refresh my memory on the postId() mechanics. A few clarifications though: 1. your structure would obviate the need for messing with the the setJ3DThreadPriority() method, am I right ? This is assuming that when the code enters the processStimulus method of a behavior, that behavior automatically hogs up all the resources ( including that of Swing ? ). 2. To the extent that I am willing to do things off of the Swing thread, shouldn't have my rought cut approach using the SetJ3DThreadPriority() method starved all J3D threads and speeded up my computations at least to some perceptible degree ? This is what is quite baffling. Does this J3D method really work under such circumstances or have I misinterpreted the doc. Regards Raj Vaidya =========================================================================== 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".
