This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Is it possible to open a new browser window in the destroy() method of an applet? I can check to see if anything's changed, and then ask the user if they want to save, and, if so, re-open the applet to allow them to save it. Can this be done?
Hi Jeff, I see 2 problems with that approach. 1. Destroy is called when the browser doesn't need your applet anymore. This is the case when the browser is closed or when the browser clears its cache. With both cases, another window will not be seen because the parent (applet or broswer) will be gone anyway. 2. Destroy is supposed to be called when the browser doesn't need an applet anymore. With browser caches, it is not exactly clear when a browser will not need an applet anymore. The destroy method is really for an applet to clean up memory resources and kill running threads that it might have spawned, etc. Regards, Manfred.