Re: quitting an applet
Re: quitting an applet
>
The problem is that the idle handler can never assume that any other
>
handler had
>
ever run.
That might normally be the case but if I am the only one who will call
this, and I will always call it (from FileMaker actually) I am using
Filemaker to be non volatile storage. And to display the results of the
workflow.
tell application "My App" to foo()
and on quitting I tell it to quit, I will need to be aware of some
abnormal launch, but it should be hard to come into play. I have one
easy check that will tell me if the init routines have been run, so I may
not need an explicit flag.
>
If your might get called after a "launch", making sure things have
>
been initialized is tricky, requiring you to set a flag, and clear it on
>
exit.
>
(Don't forget the "continue quit" statement. ;-) )
thanks again.
Doug