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?
At 04:04 PM 2/8/2005 +0000, Rolf Howarth wrote:
Either don't bother (I *think* QT shuts down reasonable cleanly of its own
accord when the application quits), or use SwingUtilities.invokeLater to
call QTSession.close() from the event loop thread.
-Rolf
At 6:37 am -0500 5/2/05, Chris Adamson wrote:
You're on Windows, right? There's a warning on page 12 that
QTSession.close() causes trouble for some people on Windows and that
QTSession.exitMovies() might be a safer way to close things down.
