One other not very sophisticated method is too translate the object
to some place far away or behind the view.
Alex.
----- Original Message -----
From: "Dola Woolfe" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, August 25, 2001 10:31 PM
Subject: [JAVA3D] Turning objects on and off: my experience
> Hi,
>
> Since I started this thread, I would like to relate
> back some of my experiences following the people's
> advice (for which I am thankful).
>
> 1. Detach/Re-attach. Predictably, this works but for
> some reason this was slower than the setVisible()
> alternative (3).
>
> 2. Make Bounds small or empty, thus excluding the
> object. For some reason this _did not_ work for me.
> Even after setting bounds AutoCompute to false.
> Perhaps I'm still missing something here.
>
> 3. Using setVisible on a RenderingAttribute object.
> This worked like charm. First, it yeilded the most
> concise code, since if you have a boolean flag for
> keeping track of the object's visibility you can use
> setVisible(false). Second, this seemed much crisper
> (i.e. more responsive) than 1.
>
> 4. Switch Node. Haven't used it yet. Seems like a
> robust alternative.
>
> Thanks for all responses!
>
> Dola
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with Yahoo! Messenger
> http://phonecard.yahoo.com/
>
>
===========================================================================
> 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".
===========================================================================
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".
