trapping quit

[Ken Ray]

> For me the issue is that in the Mac at least, a program is obliged to 
> shut down in good order when called upon to do so, for example by 
> avoiding insisting on user response (this is not the same as 
> structuring a program to put itself back into good order when 
> restarted after a crash, which is just good programming practice); 
> not sure what the etiquette is for other OSs.

Well, I ran a test where I made a simple standalone with traps in the
stack script for "closeStack", "closeStackRequest", "shutdown" and
"shutdownRequest", and had each one write a file to the "C:" drive if
they were triggered. I then ran the standalone, and chose Shutdown from
the Start menu in Windows 98. After it shutdown and I restarted, none of
the files had been written (and 'yes', I did test it to make sure it
would write before I ran this test).

So it appears that you can't trap Windows shutting down... has anyone
had any other experience with this that can shed some light on the
subject?

Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/