On 2012-03-01, John Stalberg <[email protected]> wrote: > > That would be poor communication to the user. Quit and kill is very > different and the user must be in controll over which to send. For example > any unsaved data could be lost all of a sudden if the OS killa the program > :/ And in the case were the proram is busy the user have the choise to wait > it out until it gets responsive again. > > The issue at hand here is that the OS doesn't know if the process is > temporarily unresponsive or have got stuck and need to be force quit.
Absolutely, I agree. However, I don't think Apple wants the user to have to make a decision about whether an application is permanently unresponsive, or if the system is just temporarily bogged down. Add to that, the direction Apple is taking applications where documents are constantly being saved and data loss due to suddenly killing an application becomes minimized to non-existent. I wouldn't be surprised if Apple went in the direction of allowing applications to identify that they handle documents in this way and then automatically force quitting (and perhaps then restarting) the app when it becomes unresponsive for a certain amount of time. They already do this with automatically restarting after kernel panics and power outages. -- arno s hautala /-| [email protected] pgp b2c9d448 _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
