> Date: Thu, 13 Jun 2002 19:11:29 +0200 > From: =?iso-8859-1?q?R=20CM?= <[EMAIL PROTECTED]> > > I have two "cameras" (in fact, two VP with 2 Views and > 2 Canvas) : > VP1 --> View1 --> Canvas1 > VP2 --> View2 --> Canvas2 > orb = new OrbitBehavior(Canvas2); > VP1.setViewPlatformBehavior(orb); > > and the behavior is active with the canvas1 ! > and also it's very slow. > > with the 1.2.1_03 version there are no problems...
In 1.3 the ViewPlatformAWTBehavior superclass gets its canvases from the Viewers associated with the ViewingPlatform -- we didn't deprecate the OrbitBehavior constructor which takes a canvas since the ViewingPlatform doesn't necessarily have Viewers associated with it, particularly when setViewPlatformBehavior() is called before Viewer.setViewingPlatform() is called (that was bug 4529746 - ViewingPlatform setViewPlatformBehavior throws Exception if Viewer not set before). We didn't take into account the possibility of a canvas being supplied which was associated with a Viewer on a different ViewingPlatform, so this is a definite regression on our part. We do need a test case to investigate the performance problem, though. -- Mark Hood =========================================================================== 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".
