On 1-Mar-2012, at 08:04, John Stalberg wrote: > On 1 mar 2012, at 15:05, Arno Hautala <[email protected]> wrote: >> >> I think the point is that an application that isn't responding very >> likely won't *respond* to the Quit command. If Apple changes anything >> here, I'd expect it to be by dropping the behavior of switching "Quit" >> to "Force Quit" and just have the OS send what it thinks is the >> appropriate signal; Quit if the app is responding, Force Quit if it >> isn't. > > 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.
You simply have the OS try to send a quit to the app. After a certain amount of time, send a kill. That certain amount of time is likely to be somewhere north of a minute, but south of 5. At a certain point, killing the process is the only way to continue. If the data is lost, it's already lost. -- "Remember -- that which does not kill us can only make us stronger." "And that which *does* kill us leaves us *dead*!" _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
