What to intercept for an OS closing of a stack to lock messages
bobs at twft.com
Fri Oct 5 15:51:24 CDT 2012
There is the shutDownRequest if you are quitting a compiled app. It gets sent to the current card of the main stack! Make sure you are trapping for it in the mainStack and not another. Be sure to pass it in order to complete the shutdown! My understanding is that if you don't the SIGTERM sent to the app will be ignored.
CloseStack should be working. It is sent to the current card, so make sure it isn't being intercepted and not passed through the heiarchy. I think destroyStack is a property of a stack, and not a command that does anything. It really should be named "purgeMemory" or something of the sort, as the stack is not actually destroyed.
On Oct 5, 2012, at 1:34 PM, Dr. Hawkins wrote:
> I find that, even knowing better, I tend to close my output stack with
> the OS controls (red button on Mac).
> It seems that messages are being processed; it takes, at best, several seconds.
> I've tried intercepting closeStack and destroyStack, with no luck.
> What can I do to lock messages when this happens?
> Richard E. Hawkins, Esq.
> (702) 508-8462
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode