We are using the rendering attributes with good/acceptable performance. The trick is that we turn off the rendering of the scene before we touch the attributes. After the attributes are set, we turn on the rendering again.
Pasi
-----Original Message-----
From: Discussion list for Java 3D API
[mailto:[EMAIL PROTECTED]]On Behalf Of Mona Wong-Barnum
Sent: 6. marraskuuta 2002 4:54
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] Invisibility Differences
> * use setVisible() on its rendering attributes
I tried this and it was unacceptable in that when it was making
something invisible, I can actually see the objects disappear one by one, and
the same when it was making something visible. This was unacceptable for my
application.
> * use setWhichChild() on a Switch above the shape
This was what I chose for my application; it was very fast and
remove/add back all objects at once.
> * use TransparencyAttributes
Never tried this one.
Cheers,
Mona
==================================================================
Mona Wong-Barnum
National Center for Microscopy and Imaging Research
University of California, San Diego
http://ncmir.ucsd.edu/
"The truth shall set you free, but first it will piss you off"
Gloria Steinem
==================================================================
===========================================================================
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".
