Closing, minimise and change size buttons

[RobSeegel]

362B3721440 wrote: Missed that line and don't agree! I find that very inconsistent behaviour. I have never expected n application to quit when I close the last window. Why should the last window closing behave differently to closing any other window. It is against human nature that behavoiur

Against human nature? Come on - there's no need to exaggerate to argue your point - it's just silly. I do get it - it's your personal preference, and one that may be shared by others too. Though are you really speaking for countless others, who may or may not truly share your preference? My guess is many simply don't care about the subtle difference.

I'm simply stating that this is *not* my preference, and I'm hoping that MM HD is *not* changed to behave this way. I have Applications that work both ways. I'm not claiming that your preference is wrong or even that all the apps you use that work this way are wrong.

I wanted to ensure that your preference didn't go unchallenged. When you say

Most people

and

Users

you are not speaking for me. I get angry and frustrated when I try and quit an application, confirm the quit, and the application does not quit. I guess that's just me.

[VernJensen]

You've simply been using Macs for a while, Rose. :-) Mac users expect the kind of behavior you describe. Windows users expect the opposite. I imagine that's why Apple redid their user interface guidelines to suggest quitting when the last window is closed.

QuickTime does this, and it bugs me, because it feels like Windows behavior instead of Mac, but the times are-a-changin'.

[brell]

I more or less agree with Rose, but can't it be both ways? One behaviour for Mac OS and another for windows?

[SoItBegins]

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

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).

[rose]

There are several alternatives to Quit MM so why have the red button to do it also??? At least should the window that asks if one want to suspend show up first so users doesn't by mistake quite without suspending. PC users are very used to triple confirmation on Do you really want to do this MM could in this situation at least have one.

[RobSeegel]

3A273B2D480 wrote: There are several alternatives to Quit MM so why have the red button to do it also??? At least should the window that asks if one want to suspend show up first so users doesn't by mistake quite without suspending. PC users are very used to triple confirmation on Do you really want to do this MM could in this situation at least have one.

It wouldn't bother me if the game suspended automatically if one quit while in the middle of a mansion. Seems like that would be consistent with the guidelines. The only thing with that is that it would be somewhat inconsistent with the other ways to quit - would you change these, too? If so, would there be any need for a suspend button?

[rose]

I find the suspend button very useful. Many times I play just a little, can't go on until the next saving point. I don't want to start from a saving point just because I don't have the time to play a full session between points.

[brell]

566A4C714760626C6B76050 wrote:
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.

Why does Apple want everything to behave like iPad or Iphone? What about us that are used to leave the applications on? I never quit Mail or Safari, for example.

[VernJensen]

Well, it's a debate that could continue on here for a long time. But let's keep that to some other topic outside of the beta testing area.

[brell]

475A4650350 wrote: Missed that line and don't agree! I find that very inconsistent behaviour. I have never expected n application to quit when I close the last window. Why should the last window closing behave differently to closing any other window. It is against human nature that behavoiur

Not only human nature but Nature itself! 8-)