I got to thinking about how many different ways are there for a WB script to exit. This came up in the context of: Suppose there is some code that you absolutely, positively need to have be executed at program termination. How would you do it, to ensure you catch all the cases?
Here's the list I've come up; have I missed anything?
Normal exits:
1) Reaching the end of the script
2) Executing "Exit" command
Error-type exits:
3) Hitting an untrapped error
4) Executing "Terminate" command
5) Hitting Cancel (or Escape) on a dialog
A few other possibilities I can think of off the top include a user pressing the CTRL+Break combination or calling a function that causes the user to be logged out or reboots the system.
Yeah. That's good.
Maybe I need a third category in the list for "Bizarre-type exits".
How about: The user unplugs the computer ?
BTW, there is an option in IntControl(12) to disable Ctrl/Break, isn't there?
IntControl 12 can be used to control Windows termination as well as WIL script termination. There are also IntControl 66 for logging the user out of the current session, IntControl 67 to initiate a reboot, IntControl 68 to initiate a system shutdown, and IntControl 69 to power down the system.
Yup - and I think I've used 'em all at one time or another...
Bit of a kludge, but one I've used... Write a second script that monitors the first script.
For e.g. the first script can write to a heartbeat file... if the last write was longer than x seconds ago, proceed with the Samson option (sorry, was just watching an old spy movie from 1950s...)
To handle reboot scenario... First thing the main script does is check its heartbeat file. If last heartbeat was longer than x seconds ago, launch all missiles.
...and if you are not opposed to using 3rd-Party extenders the Omnibus Extender - Sundry option has Keyboard events where you could set some key, such as ESC, to cleanly terminate a process, mid-run, or the script.
This does assume a dialog is involved.
Jim