Hi Joachim,

     The AlternateAppearance Influencing Bounds did transform
when it is using internally. That's why some of the spheres
change appearance to wireframe when the mouse drag the scene.
However, the function

     altApp.getInfluencingBounds()

will not get the transform bounds. It only get the Bounds
it is set in altApp.setInfluencingBounds(). This is
similar to other NOte getBounds()/setBounds() method.
So it is not a bug.

Thanks.

- Kelvin
---------------------
Java 3D Team
Sun Microsystems Inc.



>X-Unix-From: [EMAIL PROTECTED]  Tue Aug 14 01:43:44 2001
>Date: Tue, 14 Aug 2001 10:43:40 +0200 (METDST)
>From: Joachim Diepstraten <[EMAIL PROTECTED]>
>To: Kelvin Chung <[EMAIL PROTECTED]>
>Subject: Re: [JAVA3D] Hmm Bounds...
>MIME-Version: 1.0
>
>Hi Kelvin
>
>> >Well maybe my description was abit misleading I actually meant the
>> >influencingbounds not the bounds? If the same applies to the influencing
>> >bounds I can send you a test case.
>>
>> It should also transform as well. This will be great to have
>> a test case for us.
>Allright I've attached you a small test programm it's basically a
>modification of the AlternateAppearanceBoundsTest-demo provided by
>Java3D. Added a TG and a MouseRotator and some system outputs to make
>things clearer.
>
>Hope it helps
>
>EOF,
> J.D.
>
>--
>Jmark2k+1 (http://www.antiflash.net/jmark)
>Test the performance of your PC online!

===========================================================================
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".

Reply via email to