Re: Help with droplet
Re: Help with droplet
- Subject: Re: Help with droplet
- From: Emmett Gray <email@hidden>
- Date: Wed, 4 May 2005 02:42:51 -0400
Is
On Tue, 3 May 2005 18:36:51 -0700, Jon Pugh <email@hidden> wrote:
At 11:09 PM +0100 5/3/05, kai wrote:
I find myself somewhat at odds with the ASLG on this one, Emmett -
since it appears to suggest that forcing a quit saves changes to
script properties and quits immediately (bypassing the script's
quit handler):
http://developer.apple.com/documentation/AppleScript/Conceptual/AppleScriptLangGuide/AppleScript.e8.html
The ASLG is not talking about force quitting. It is talking about
quitting with the shift key down, which bypasses the script
application's "on quit" handler. In this case, properties are still
saved.
Is there a way to trap this behavior? In my droplet, it could cause a
disaster if properties were saved in the state they were in in the
middle of a run. They absolutely have to be saved in their original
(or "on quit" reset) state if I'm going to use them at all. Or else I
need some other mechanism so a droplet can know if it is starting up
the "on open" handler for the first time so it can reset the
properties when first launched.
--Emmett
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden