Skip navigation

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

3550 Views 37 Replies Latest reply: Jul 1, 2012 4:28 PM by Jean-Marie Allier RSS
  • petermac87 Level 5 Level 5 (4,065 points)

    True but not for recent converts to Apple which is a Hugh market these days with iPhone and iPad integration, so they are not going to continue to give their main focus to old users who will start dying out. Not good business.



  • petermac87 Level 5 Level 5 (4,065 points)

    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?



  • Shootist007 Level 6 Level 6 (16,640 points)

    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.

  • WarrenO Level 1 Level 1 (5 points)

    petermac87 wrote:


    Sorry, I do not recall responding to you.



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

  • petermac87 Level 5 Level 5 (4,065 points)

    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



  • cdevers Calculating status...


    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?




    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.

  • petermac87 Level 5 Level 5 (4,065 points)

    Menu top left, Apple drop down, and file bug report of you are suspicious.



  • cdevers Level 1 Level 1 (0 points)

    Well, yes, naturally. (Or use Radar for that matter.)

  • petermac87 Level 5 Level 5 (4,065 points)

    Maybe you should be posting in the developers forum then. And why would people gripe when the vast majority are having no problems with Lion



  • WarrenO Level 1 Level 1 (5 points)

    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.


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.