Tim,
In my experience it's not really worth doing very much at all... I hope I am
wrong about this but I tried all kinds of combinations and could never get
our Applet to respond properly to multiple page refreshes. The applet would
(usually) disappear after half-a-dozen refreshes regardless of how I handled
the various callbacks.
I tried all sorts of elaborate schemes to kill Java 3D, without success. I
forget the details (search the archives) but eventually the Canvas3D ends up
*behind* one of the Plugin Windows...
I reported this problem (as did others) many months ago.
Sorry to be a bearer of bad news.
Sincerely,
Daniel Selman
[EMAIL PROTECTED]
http://www.tornadolabs.com
-----Original Message-----
From: Discussion list for Java 3D API
[mailto:[EMAIL PROTECTED]]On Behalf Of Tim Bray
Sent: 17 November 1999 19:41
To: [EMAIL PROTECTED]
Subject: [JAVA3D] Stopping J3D
If I'm running in an applet, what are the sensible things to do, J3D-wise,
in the stop() and destroy() methods? In stop() presumably I want to
preserve my scene graph but tell all the J3D threads to stop running.
In particular things like KeyNavBehaviors with that are essentially polling.
Or will the browserr somehow automagically make this happen?
In destroy(), I want to free up the scene graph - I guess doing
surgery on the SimpleUniverse() to detach my locales and viewing platform
is in order?
Or does all this take care of itself? -Tim
===========================================================================
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".
