ModelClip planes seems to loose their association with the transform of its
containing TransformGroup under some circumstances.
In my application I can switch the mouse between controlling the position
and orientation of each of a set of objects, or the users overall view
perspective. The mouse behaviours associated with the transformations of
each object or the viewer are switched accordingly. Everything works fine
until...
One of the objects (the Sectioning Object) consists of a ModelClip plane
with some additional objects (a grid of boxes so that I can see where the
ModelClip plane is).
If the Sectioning Object (containing the ModelClip Frame) is the initially
current (mouse controlled) object then the mouse will correctly control the
position/orientation of that object including the ModelClip plane and the
grid of boxes. However, once the mouse is switched to control something
else (ie the mouse behaviours associated with the transform group in which
the ModelClip resides are disabled) and then switched back (the mouse
behaviours are reenabled), the solid components in the Sectioning Object
(the grid of boxes) again correctly moves, but the sectioning plane does
not. It is left frozen relative to the viewer at its last location.
I can work around this by deleting and recreating an identical clip frame in
the sectioning group each time the sectioning groups mouse behaviours are
reactivated but this
Is this a known bug and if so, what is the minimum requirement to reset the
clip planes accociativity with its owning TransformGroup?
Thanks for any info
Alex Bowden
===========================================================================
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".
