Re: Can't quit from Dock or cmd-Q
Re: Can't quit from Dock or cmd-Q
- Subject: Re: Can't quit from Dock or cmd-Q
- From: has <email@hidden>
- Date: Fri, 25 Oct 2002 00:50:21 +0100
Paul Berkowitz wrote:
>
I can't quit a repeat loop from a non-stay-open script application by
>
selecting Quit in the app's icon in the Dick
Ouch. Sounds painful... ;)
-----
>
(command-period) works fine. Force-quitting works. Has it always
>
been the case that cmd-Q doesn't work, or is it new in OS 10.x?
It was ever thus.
NOTE: User-cancel != quit. Force-quit != quit.
'Quit' is polite and civilised: it doesn't interrupt other operations that
are currently underway. Instead, it waits till those operations have
finished before shutting down the whole process. If your valuable database
application is performing some sensitive data processing operation, you
don't want it to drop everything it's doing and crash to a chaotic halt.
You want it to finish that work first, and only _then_ shut down in an
organised fashion.
This is the total _opposite_ of user-cancel/force-quit; both of which
effectively translate as "Aaaaargh! Everything's going totally to hell, so
get out NOW before things gets any worse!" These two are most definitely
_not_ polite or civil, but sometimes they're your only realistic option. [1]
...
I recall the same question being asked several times in the past, so
there's obviously some confusion over how 'quit' actually works. (As usual,
I blame the AS literature: either it doesn't explain it at all, or doesn't
explain it well enough. But what's new?) But the way it does is sensible
and correct.
(I could rattle on about batch-process and event-driven systems which might
help shed a bit more light on the 'whys', but hopefully this is enough to
explain the 'what'.)
-----
>
where exactly is the bug?
The bug is that a non stay-open applet should show a 'Quit' option at all;
it's quite inappropriate. If that's happening in OS X (it doesn't in 9),
I'd suggest submitting it to Radar (i.e. you've found a bug, it just wasn't
the one you were thinking of:).
HTH
has
[1] Related note: osax commands such as 'display dialog' and 'choose file'
are _way_ too quick in raising errors for inadequate reason. 'Choose from
list' _almost_ gets it right, but drops the ball by making its single
return value do more than one thing (i.e. return a list if OK is clicked,
but 'false' if 'Cancel' is chosen). The proper behaviour for all would be
to return all results within a record, the first property of which was
{cancelled:true/false}. [Note that scripters are also a bit prone to using
deliberate errors and error trapping for "normal" flow control (e.g. me).
For once, AS is better behaved than we are...;]
--
http://www.barple.pwp.blueyonder.co.uk -- The Little Page of AppleScripts
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.