Thanks, Rajesh, for shining light on this subject.
I plan to use external JFrames until Sun fixes the design.
-----Original Message-----
From: Rajesh Gupta <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Saturday, July 17, 1999 12:50 PM
Subject: Re: [JAVA3D] MDIs and Java3D (Was: Re: [java3d] Canvas3D allways on
top!!!)
>Hi Andrew,
>They have been thinking of adding a heavy JInternalFrame for more than a
>year now. They have no official commitment to provide it. They had just
>mentioned it in the Lightweight Heavyweight page at the Swing connection
>more than a year ago. That they just might provide such an option. So, I
>don't have any hopes from the swing team for providing that.
>I had talks with some guys in Java development from SUN last september and
>we were really pushing for a solution to this problem. They said, they
might
>provide a flag in all swing classes ( Just like JPopupMenu) which would
>allow them to be heavyweight. But, they also said, that this was low on
>their priority list and there was no commitment from their side. Also,
since
>it required API changes in a core part of JDK, that was another problem.
>
>JDk1.2 and swing is still full of bugs, so I guess before pushing for any
>API changes, for now, they are more busy in getting the existing API's
>stable. Also, since swing is a part of JDK. Any API changes should not be
>possible before a new version of JDK.???? Maybe in JDK1.3.
>
>As I already mentioned. A fairly good workaround should become available
>with JDk1.2. JD1.2 will support rendering to an offscreen buffer. In that
>case, you can render to an off screen buffer and simply update the contents
>of your light canvas (JComponent) in the Internal frame with the contents
>from this buffer. Of course you will might to slightly modify your mouse
and
>keyboard behavior classes.
>In another of my mails to the list ( ????Or did I only use reply and not
>reply all). I had outlined a workaround for this problem that I have used
>successfully. That involves copying the contents of a canvas 3d to a buffer
>as the enclosing internal frame is moving back and replacing the canvas3d
>with a Jcomponent which draws these saved contents. This won't work if you
>have any non-input behaiors.
>
>Try to avoid MDI for now. If you absolutely must use MDI, try something
like
>Visual Cafe, ie, floating frames instead of JInternalFrames.ie, you have a
>bar on top having menus and toolbars. All the child windows appear as
>separate frames on the desktop.
>Let's pray for this one. That the J3D 1.2 becomes available soon and
>provides support for off screen rendering.
>
>Regards,
>Rajesh Gupta
>
>
>----- Original Message -----
>From: Andrew R. Thomas-Cramer <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, July 12, 1999 8:27 PM
>Subject: Re: [JAVA3D] MDIs and Java3D (Was: Re: [java3d] Canvas3D allways
on
>top!!!)
>
>
>> Rajesh:
>> Thanks very much for responding.
>>
>> All:
>> The Java3D FAQ at http://tintoy.ncsa.uiuc.edu/~srp/java3d/prog.html
>says:
>>
>> "Don't use JInternalFrames. No workaround for this problem yet,
>but
>> the Swing
>> team is thinking of adding a heavy JInternalFrame option."
>>
>> Does anyone know the status of this possibility, and, if still viable,
>in
>> which release
>> it's planned for inclusion?
>>
>
>===========================================================================
>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".
