08-11-2011, 10:07 AM
Regarding what Rob posted, here's a full explanation of what's going on.
Advisory: The next few paragraphs are going to be kinda technical.
I read the review of Mac OS Lion. They changed the way things work, a bit. For starters, all (normal) documents are autosaved. All the time. Multiple versions thereof, so that the user doesn't mistakenly find the computer's saved over their work.
With documents autosaved, apps can restore you to exactly what you were doing when they were last quit. No closing all files before you quit, no
A third big change is a toolkit that allows apps to signal when they're not processing data or something similarly non-interruptible, and thus the computer is allowed to quit them if it feels the need to do so. By itself, this would be minor.
However, the crux of the thing is a new method of application handling in Lion: If an app supports exact resuming, and supports letting the computer know when it's OK to quit, the computer then reserves the right to quit the app at any time when there are no non-minimized windows onscreen. After all: the app's not getting in your way, and when you click to resume everything'll come back perfectly as you left it, right?
(The app's icon and those of minimized windows remain in the dock, by the way. They just don't have anything attached to them in a back-end sense.)
The short version is, Lion will automatically take care of the 'last window close = quit' issue, assuming the app supports resume and letting the computer know when it's OK to quit. Ideally, programs built for Lion also save automagically and only run on request, restoring their data perfectly if they were quit (by the system) and started again (by the user).
If this sounds familiar to you, you've probably already been experiencing something like it on your iPad or iPhone.
Of course, what I've said does nothing for the what-the-button-does debate.
I would suggest that clicking on the red button requests confirmation to exit, then quits the game (it really doesn't make sense for this game to hang around after its window is closed, as all it could do after that would be to bring up a new window).
Advisory: The next few paragraphs are going to be kinda technical.
I read the review of Mac OS Lion. They changed the way things work, a bit. For starters, all (normal) documents are autosaved. All the time. Multiple versions thereof, so that the user doesn't mistakenly find the computer's saved over their work.
With documents autosaved, apps can restore you to exactly what you were doing when they were last quit. No closing all files before you quit, no
do you want to save?— instead, quitting becomes a sort of pause between work sessions. When you reopen the app, everything is exactly as you left it.
A third big change is a toolkit that allows apps to signal when they're not processing data or something similarly non-interruptible, and thus the computer is allowed to quit them if it feels the need to do so. By itself, this would be minor.
However, the crux of the thing is a new method of application handling in Lion: If an app supports exact resuming, and supports letting the computer know when it's OK to quit, the computer then reserves the right to quit the app at any time when there are no non-minimized windows onscreen. After all: the app's not getting in your way, and when you click to resume everything'll come back perfectly as you left it, right?
(The app's icon and those of minimized windows remain in the dock, by the way. They just don't have anything attached to them in a back-end sense.)
The short version is, Lion will automatically take care of the 'last window close = quit' issue, assuming the app supports resume and letting the computer know when it's OK to quit. Ideally, programs built for Lion also save automagically and only run on request, restoring their data perfectly if they were quit (by the system) and started again (by the user).
If this sounds familiar to you, you've probably already been experiencing something like it on your iPad or iPhone.
Of course, what I've said does nothing for the what-the-button-does debate.
I would suggest that clicking on the red button requests confirmation to exit, then quits the game (it really doesn't make sense for this game to hang around after its window is closed, as all it could do after that would be to bring up a new window).