User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
I haven't noticed any ill effects from only using exitMovies. Not
using it can keep the app from exiting. But using close always
seems to do bad things.
Laura Ferguson wrote:
>
> In Chris's book this code is already occurring as a shutdownhook. If
> changed to an invokeLater wouldn't this code occur after shutdown and
> therefore not occur?
>
> So I'm still not convinced either way. I'm gathering that we have three
> choices:
>
> A) SwingUtilities.invokeLater with a QTSession.close in the event loop?
>
> B) Runtime.getRuntime( ).addShutdownHook(shutdownHook);
> where the shutdownHook calls QTSession.close or
> QTSession.exitMovies?
>
> C) Do nothing and hope that it all shuts down automatically when the
> application closes.
>
> I read the same jdocs for exitMovies, and I'm not clear on what
> exitMovies really does, can anybody "in the know" clarify the role of
> exitMovies vs. close? Does exitMovies include the close action?
>
> Lastly, perhaps we don't need close anymore. How can we evaluate this?
> What would indicate that close was not properly called on Windows or OSX?
---------------------------------------------------------------------
Kevin Weiner FM Software 610-997-3930 http://www.fmsware.com
