Message: 2
Date: Wed, 27 Nov 2002 11:52:13 -0500
Subject: Re: Quit on Mac OS X
From: Rick Harrison <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
I had this same problem as does probably a lot of others
on the list.
In my case there were only 2 times when it was critical to
know which quit happened to update my preference files for
the user. That happened to be on the very first run of
the program and at registration time. The solution for
me was to force my own "File Quit" if the user was doing
any of these two processes. The rest of the time it didn't
matter at all for my particular application.
The only other work around for me would have been to eliminate
my own "File Quit" and to do my updating long before the use
ever quit my application.
Hope this helps!
Rick Harrison
The only possibility I know is to trap the corresponding AppleEvent :
on AppleEvent the_Class,the_ID,the_Sender
if the_ID = "quit" then
do_whatever_you_wish
quit
else
pass appleEvent
end if
end AppleEvent
Regards
Herve Proudhon
----------------------
Diondine, logiciel de di�t�tique
http://www.diondine.com
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
