You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Is it possible to disable the auto quit of preview and other apps?

This "Apple thinking for me" has got to stop. Does anyone know how to disable the auto quitting of apps after the last doc is closed and another app is clicked on?


I know it happens in Preview and it's terribly annoying since you can't turn it off.


Anyone?


Lion bothers me severely.


Even went to the Apple Store to buy another copy of Snow Leopard so I can revert back and they don't carry it any more.


This is an infuriating operating system.

Mac OS X (10.7), Mail app

Posted on Aug 2, 2011 10:33 AM

Reply
Question marked as Top-ranking reply

Posted on Aug 2, 2011 12:27 PM

Unfortunately this behavior is the new Apple recommended normal and expected behavior, according to Apple's own Human Interface Quidelines:

In general, quit when users close the last open window in your app. In apps that are not document-based, users generally expect the app to quit when they close the main window. If an app continues to perform some function when the main window is closed, it might be appropriate to leave it running after the user closes the main window. For example, iTunes continues to play after the user closes the main window. If users close the last remaining document window in a document-based app and switch to another app, it’s appropriate to quit the app.

Currently the applications that are showing this behavior are Preview, TextEdit, and QuickTime Player X. There may be others, and there will certainly be more in the future, if the above recommendation means anything.


For the morbidly curious, the whole PDF is here:


https://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual /AppleHIGuidelines/Intro/Intro.html#//apple_ref/doc/uid/TP30000894-TP6


And I don't much like it either.

Francine

38 replies

Mar 26, 2012 7:02 PM in response to Shootist007

But you see, long time Mac users haven't come from Windows. We have been using apps where you actually launch and quit them yourself for up to oh, about 27 years.


Even if you have only been using it since OS X, that's 12 years of reinforced behaviour.


It's like driving a car. You start it yourself. You turn it off yourself.


Apple should at least have a system wide preference before it screws with decades of user experiences.


If you had an app open for the explicit purpose of using its GUI to open files, this removes that functionality.


And, the bad bart of it is that the app is still running, (check the Activity Monitor). You're simply prevented from using the GUI if the app has no documents and you've moved another app frontmost.

Mar 26, 2012 7:08 PM in response to Alex Zavatone

Alex Zavatone wrote:




Apple should at least have a system wide preference before it screws with decades of user experiences.



So you know that it possible given the new coding within Lion and the upcoming Mountain Lion? Or are you just guessing that the possibility to reinclude this feature and the other dozen or so old features that a few others want returned will actually even work if embedded within the newer code?


Pete

Mar 26, 2012 7:10 PM in response to Alex Zavatone

Alex Zavatone wrote:


But you see, long time Mac users haven't come from Windows. We have been using apps where you actually launch and quit them yourself for up to oh, about 27 years.


Even if you have only been using it since OS X, that's 12 years of reinforced behaviour.


It's like driving a car. You start it yourself. You turn it off yourself.


Apple should at least have a system wide preference before it screws with decades of user experiences.


If you had an app open for the explicit purpose of using its GUI to open files, this removes that functionality.


And, the bad bart of it is that the app is still running, (check the Activity Monitor). You're simply prevented from using the GUI if the app has no documents and you've moved another app frontmost.

Well logic, at least my logic, says to me that when I am done usiing a program and I close the window I am working in the program closes with that window.

The old Apple way is like I drive my car into my driveway and turn the key off but the car keeps ruinning. The key just locks the wheels from turning.

If I'm done watching TV and shut the TV off I don't just want the screen to go black.


It's not just because I come from Windows. If I had never used a computer before I would fine this practice of leaving program open to be very strange.

Personally I'd like see every program do this. I wish there was a setting to do this.

Mar 26, 2012 7:36 PM in response to Shootist007

So Shootist, Apple's GUI has this "functionality" people sometimes use. The Open window lists your recently accessed folders and even has a search function in it. You can command tab to a running app and actually (god forbid) use that functionality to open files in recently used folders. That's a great reason to use an app open and an app like TextEdit or Preview use 9 MB when open with no docs.


9 MB. That's it under Snow Leopard.


15.4 MB in Lion.


And when you click on the Finder when TextEdit has no docs open, it appears the app quits, but it is still running and it STILL takes up 15.4 MB. No memory is being saved. If any memory is saved at all, only up to 300 K is saved. That's the most I've seen in my tests in the differenve between TextEdit running in Lion with no docs and clicking in the Finder to fake quit TextEdit.


It's not even a real quit where your Mac gets all the memory back. It's still being used.


So, Lion keeps the app running in the process monitor but disables the GUI, all so that it will "launch faster" the next time you launch it. And you still have to locate and double click on the app and wait a few bounces before the app launches. This is another delay I don't want to deal with. I'm a big boy. I'm all grown up now. I know how to quit an app. It's called command Q and it gives me all the app's 15 MB back.


See, I didn't tell the Mac I didn't want to use the app's GUI any more and that Apple should disable it but keep the app running.


This issue would be EASILY solved with a system level preference to have apps auto quit upon closing the last doc and bringing another app front most, or not to fake quit the app.


It's not a quit. It's a fake quit. The only thing disabled is the GUI. The memory the app uses is still used.


If Apple offered an OPTION as to whether people wanted to use this option in System Prefs, this wouldn't be an issue, because I could turn it OFF and you could turn it ON.


This is not that hard to do correctly and keep both sides happy. It's kind of very NON Apple that they don't seem to care about preferences of the their own long term customers who actually used the OS the way they fostered over the past two plus dacades.


Look, you decided that you wanted to start up the app yourself, didn't you? You can also make the decision to stop it yourself, just like how you put your computer to sleep and just like you tell your computer to shut down or restart.


But at least give the users who had the previous preference a choice in a system preference.

Mar 26, 2012 7:49 PM in response to WarrenO

WarrenO wrote:


petermac87 wrote:


Sorry, I do not recall responding to you.



Tough. It's an open discussion in a public forum.

True, which gives us a choice of not bothering to reply to the uninformed or trollers around the place, which I try hard not to, but they just like their little say to feel important.


And Alex


If Apple offered an OPTION as to whether people wanted to use this option in System Prefs, this wouldn't be an issue, because I could turn it OFF and you could turn it ON.



As I said before, if you are so sure that this option willbe completely compatable with Lion and Mountain Lion, then tell them. All their developers may have overlooked this. Or possibly, they couldn't write it into their code. Not sure which one is most likely.


But you are both fighting a loosing battle and going back to Snow Leopard would be your answer or wait for Mountain Lion and hope they have rewritten the entire system's GUI for both of you.


Good luck and good bye


Pet

Mar 27, 2012 8:12 AM in response to petermac87

petermac87


cdevers wrote:


I've had Lion on my laptop for a day and I already hate it, mostly due to this "feature" and the way it keeps killing processes with network connections (SSH, VNC, etc). The problem isn't just with TextEdit and Preview, the way some of the discussion (e.g. on TidBits) says, but with any processes, including command line tools. I tend to leave long-running programs open for days or weeks at a time, and under Lion I can't trust them to be there when I come back to that window. This is unbelievably frustrating.

Good to see you are giving it time to get used to it. There is absolutely nothing wrong with Lion. Mountain Lion is due out soon, something that most people in this very old thread would not have known when posting here. Nothing will be going 'backwards' in ML as most people, as per usual, have become very familiar with the GUI of Lion except some who refuse to acknowledge change.


So the best I can advise is to completely wipe your harddrive and reinstall from the Snow Leopard Backup you made yesterday and stick with Snow leopard until you feel comfortable in handling the new systems.


Good Luck


Not quite sure why I'm feeding the troll here, but thank you for your constructive response, petermac87. It's heartening to see that an observed & reproducible bug is not, in fact, an observed & reproducible bug. Heaven forfend that there be observed & reproducible bugs in OSX. And your "best" advice, to wipe & reinstall the operating system, why, more constructive advice has never been given, no?


Ahem.


So anyway, yeah, this behavior is a bug. I am not a new Mac user, and this isn't my first exposure to Lion. The way shell commands would continue running normally going all the way back to the OSX public beta in 2000 was entirely reasonable & predictable, and in keeping with all other reasonable & predictable POSIX-ey platforms (Linux, Solaris, BSD, Irix, BeOS, Cygwin, etc). It worked. It was fine. That's what brought me to Macs full time in the first place.


It's possible that I'm misinterpreting what's going on here. All I can say definitively is that under Snow Leopard, I could reliably open SSH shell sessions to remote hosts, and that connection would stay open to use in any arbitrary way. Now, under Lion, the session silently dies after a period of "inactivity", where "inactivity" appears to be defined as "user input". So even if I'm leaving something running to watch the output of some command (e.g. `top`), the SSH session will terminate and kick me back to a local session in the shell window.


It's not, I think, that Terminal itself is quitting, nor is it that Terminal window processes are being killed like you see with the new multi-process version of Safari and how it kills idle windows. If you, for example, quit & relaunch Terminal, then you get back the previous windows & text, but everything from the previous session is greyed out. That isn't what's happening here: the GUI session remains open, but the CLI processes are vanishing, with huge negative side effects.


But at least it's not a bug. That's a relief.

Mar 27, 2012 3:48 PM in response to petermac87

Because I am a registered developer and I read the docs. Also, if it were not supported, then every app that is compiled for Lion would automaticaly quit when the last doc is closed and the app becomes sonething other than the frontmost app.


Automatic and Sudden Termination are documented in the NSProcessInfo_Class.pdf document and control is given to the developer.


However, it appears that the system overrides the developer settings for certain apps (TextEdit and Preview, I believe) and no matter what you've set in the application's preference pList or in the code of the application, the system sets these on, overriding the user or developer's control.


Apple's gone overboard to make this much more difficult than one would expect.


If I have time tonight, I'm going to take the TextEdit source, change some application identifiers and see if I can get the build to obey my wishes. But really, we should not have to go to such extreme efforts to get the apps to behave as we have always expected if we wish this to be the case.

Mar 27, 2012 4:59 PM in response to petermac87

petermac87 wrote:


And why would people gripe when the vast majority are having no problems with Lion


Did you just ask why an individual would have an opinion that doesn't happen to match what everyone else thinks?


More seriously, though, a better solution would be to let us, individual users, choose our systems' behavior. The default could remain auto-'quit' (and even that gawdawful 'relaunch [programs] when logging in' selection), but we'd have the choice in system settings to turn off one or both. (Why the latter? Try having your machine crash while you're running some or all of Adobe's 'Creative Suite', then sit back and wait the extra ten minutes necessary for your desktop to finish reloading after you've rebooted, before you even have a chance to address what went wrong or run any repair utilities.)


That's really what this is about - users being able to take control of their machines and have them do what they want and expect them to do. A dual quad 8 GB 27" iMac is not an iPad, and there is no particular reason for its native programs (or any other programs) to behave as though it is.


I think I can understand why Apple is merging some iOS ideas with OSX - but not every idea is a good one, and not every metaphor ports. Auto-closing programs on iOS is necessary, because of UI constraints and raw machine muscle (or lack thereof). Such behavior is not necessary on a desktop system, nor is it automatically desirable, regardless of what other users might be familiar with.


There's a reason we don't use mice with iOS. There's a reason why auto-quit (and auto-resume) may not be desirable on a desktop system. Please consider the possibility that it's more productive to consider the validity of these concerns, than it is to take a hardline canonical approach that suggests, in essence, that Apple's UI decisions are always right, and Cupertino can do no wrong.

Mar 27, 2012 5:55 PM in response to petermac87

Maybe you're not using a magic mouse. Maybe you don't have a workflow that Apple's changes have affected.


I've talked to people who are not you who say that Lion's changes have caused a fair amount of problems for many people.


So, I think you are making a generalization saying that the vast majority of people are using Lion (or Lion Server) with no problems.


Lion Server didn't ship with the basic utilities that Snow Leopard Server did.


In Lion, turn off gestures. Using a magic mouse or or trackpad around the edges of Safari causes the screen view to wobble - even if Gestures is off - if the trackpad or magic mouse thinks it detects a pinch. Even if Gestures is off.


If Gestures is on it's all too easy to mistakenly have your Safari text to get larger and smaller through a mis detection of a pinch. I never had this problem before. I almost NEVER change the size of my text in Safari. Who would think that anyone would want to do this in Safari on a reoccurring basis? Terrible, terrible feature.


Why can we not turn off gestures on a per app basis?


In Safari, I keep the downloads window open and select my downloads from that. Apple's removed the window capability and you can't press command option L unless there has been a download in the queue. The menu item has moved from Window to View and it is missing if nothing has been downloaded or the queue is empty. This is inconsistant functionality.


Can't turn off the bouncing scroll bars (elastic views). This is terribly annoying when scolling with inertia. I'm not on an iOS device. Stop animating the screen when I could be interacting with it. Is thre a switch to turn it off? No.


The desaturated icons in the Finder make it harder to tell if a GUI element is enabled or disabled.


I like my blue scroll bars over the gray ones. What, do I have to hack that to turn tham back too?


Animated EVERYTHING. I realy hate email messages zooming up off the screen on my 27 inch screen. It's startling, distracting and unpleasant. Can I turn it off? Not without finding some hack.


Alerts and dialogs popping open in my face. Annoying. A setting to turn it off? Nope. Gotta find some hack.


Code signing of some apps prevents you from opening and changing ANYTHING in the app. If I change 1 byte in TextEdit, even if I built and codesigned the app with my dev license, it crashes on launch.


Safari windows popping open in my face. Again, distracting and annoying on a 27 inch screen. Can I turn this off without resorting to a hack? Nope.


Bounce is something I've used in Email for years to bounce political emails back to my friends and family members who forget I don't want that. It's gone. Screw you Apple. You remove something I use every day. Why should I pay to have functionality I use removed?


At this point, this is not an enjoyable OS to use, if every window open is startling and annoying and you can't easily turn it off AND you paid for this.


Xcode 4.3 on Lion removes distributed builds. W T F? I am not amused.


Ugly Address Book and Calendar.


Automated quitting of some apps.


Downloading something in Safari throws something across my screen. OMG, stop this.


No simple friendly Apple setting to TURN OFF ALL THE GRATUITOUS ANIMATION. I want a fast OS so I can zip through my tasks. Just display it as fast as you can, or give me the ability to disable it.


In the Finder, lots of the command control 1, 2, 3 shortcuts that I use many times every day to sort the Finder List Window contents were broken as of the first two releases of Lion.


Air Drop was non functional when using Lion and Lion Server in the initial release.


At this point, it's simply foolish to move to the OS if it is this annoying and it makes it an issue to set the specifics back to what worked for you.


That and the previously selected window in Safari would scroll when scrolling by the middle button on the magic mouse.


This is all what I encountered when using Lion and many of these irritations still exist today.


At this point, what's the point of spending more time with the OS if I value my time and if I value how I feel when I use the computer? I use a Mac because I LIKE IT, because it helps me get my job done fast with a reinforcing and pleasing OS, not because I want it to annoy and irritate me.


So, you're telling me that spending 30 bucks to then WASTE TIME to try and turn all these settings back since Apple doesn't offer simple switches to do so actually makes sense? Lion isn't worth the time if I have to spend 1/3 of an hour (20 minutes) doing so. I've lost money if I have to spend any more then 20 minutes messing with the OS. See, the only reason we buy the upgrade is because it is supposed to HELP US so what we do better.


If the OS gets in the way of our using the computer then it's not really helpful, now is it?


Yes, Apple knows about my issues. Again, I'm trying to see if I can disable this auto app quitting in case we forget the point of this thread. If you have any input on how to do that, then please let me know. Saying that "the vast majority of users don't have any problem with Lion" simply shows that you're not paying attention to users who are used to the Mac OS and/or are light weight users who don't have an established workflow. It also shows that you know how to make passive/aggressive belittling generalizations and enjoy going that. I don't care. I'm trying to restore familiar, predictable and standard functionality that I've been using in the OS since 2000. If you can help on that front, then great. If not, we've discussed this enough.

Mar 27, 2012 6:16 PM in response to Alex Zavatone

Re animation disabling - have you given TinkerTool a look? It has a fairly good set of controls for overriding at least some animations:


http://www.bresink.com/osx/0TinkerTool/details.html


Doesn't do anything about automatic program quitting or launching, though. The script I wrote wiill shut down a Mac and purge the 'automatically load programs when logging in' history, and it can easily be modified to do that on reboot as well - but it assumes a normal shutdown. If you have to force a reboot, it won't work.

Is it possible to disable the auto quit of preview and other apps?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.