Hi, The com.sun...pick behaviors like PickRotateBehavior, for example, take a Canvas3D object in their constructors. The canvas is used to create a PickCanvas which in turn is used to determine what object to perform the behavior on, such as rotating an object.
That's fine, but what if I have more than one view on my virtual world and I want to be able to rotate objects from any one of those views.
Should I create a behavior for each different canvas? Or should I have a single behavior and change the PickCanvas being used by that behavior according to which canvas is the source of the mouse event?
What is the conventional wisdom on this matter?
If I have multiple behaviors, since they are all added to the scene graph at the same point, they all receive notification that a mouse rotate event has occurred - regardless of the canvas. Should I filter out those events not emanating from the associated canvas or will the fact that the pickCanvas is not appropriate anyway take care of that for me?
Bottom line - what's more efficient: multiple behaviors, one for each canvas -or- single behavior and keep switching the PickCanvas?
Many thanks, -Paul
=========================================================================== 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".
