Can someone explain to me why the functionality of Transform3D isn't just
built into TransformGroup? A TransformGroup always has exactly one
Transform3D associated with it, doesn't it? Is there any way to use
Transform3D other than as a component of a TransformGroup? Wouldn't it
save quite a lot of typing (maybe also memory - fewer objects to deal
with?) to have these integrated into one object?
Apologies if I'm being dense here...
- Fergus
http://fergusmurray.members.beeb.net/interact.htm
beauty through mathematics
===========================================================================
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".
