Kelvin, I could kiss you. But, since I'm in Omaha Nebraska, and you're probably somewhere much nicer, it will never happen. Anyhow, you mentioned the following:
"Looks like an MT-safe issues when using SharedGroup, please send us a complete test case." As you had successfully presumed, the TransformGroup that was the target of the RotPosPathInterpolator has some Link nodes and those Links all pointed to the same 3D model (in a SharedGroup). Now, what was interesting was that elsewhere in my code, when I chose to stop displaying one of those 3D models, I did the following: link.setSharedGroup((SharedGroup) null); And that command stopped one of the 3D models from being displayed in the scene graph. Everything was still good, but now when I put that TransformGroup (that contained all the links) as the target of the RotPosPathInterpolator, Java3D must iterate through all the nodes, and having a link with a null reference caused the NullPointerException. My question to you is do you still want a test case? Or is it programmer (my) error? I reread the Link API and didn't see anything about a null shared group being illegal, so I expect that Java3D should check for a null SharedGroup before accessing it. (Or should the "bug report" just be an enhancement to the documentation/API to make illegal a null SharedGroup) Much thanks, David B. =========================================================================== 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".
