On Sun, 13 Dec 1998, Leo Cyr wrote:
> If you use HotJava (current is 1.1.5) for some reason ;-) it automatically
> re-downloads the classes/jars specified in the Applet tag. I'm not sure why
> -- I guess it is realted to the browser's cache, but caching of html is
> still on... It just works...
>
> Christopher Hinds wrote:
>
> > Since the browser caches HTML pages in a history list of some type,
> > every
> > you time leave and return to the HTML page, the applet will be activated
> > ( start() ) and deactivated ( stop() ) respectively. Therefore you can
> > try clearing the cached pages which should force the embedded JVM
> > to call the destroy() on the applet. Or you can uses JavaScript to
> > clear the browser cached history
> > list if the browser supports JavaScript.
> >
> > Cheers
> > Chris
> >
> > Thor Erik Karlsen wrote:
> >
> > > This is a proplem that has been irritating me since the day I started
> > > developing applets(not that long ago). Is there a WORKING way an
> > > applet can destroy itself and tell the browser that its dead? I always
> > > have to start the browser again and reload the applet during
> > > development. Destroy() dont work. What im looking for is some code
> > > within the applet that solves the problem once for all. Thor Erik
> > > Karlsen
> > > Catalyst ONE AS
> > > [EMAIL PROTECTED]
afaik the applet can't do it, but the user CAN.
With netscape, hold the shift key down while clicking "reload."
Or use the appletviewer.
--
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.
