Pete,
You are correct. Geoff Canyon showed me that lock messages is set before the
stack is closed and removed from memory so the closeStack message is never sent.
Fortunately Shao Sean pointed out the command revIDEHandleObjectDeleted is
sent. This is what I use in a front script in my lcTaskList plugin.
command revIDEHandleObjectDeleted pObject
if the first word of pObject is "stack" then
put the short name of pObject into vTarget
if vTarget begins with "rev" then --skip Rev's stacks and dialogs
--do you action here
end if
end if
pass revIDEHandleObjectDeleted
end revIDEHandleObjectDeleted
Bill Vlahos
_________________
InfoWallet (http://www.infowallet.com) is about keeping your important life
information with you, accessible, and secure.
lcTaskList: (http://www.infowallet.com/lctasklist/index.htm)
On Aug 4, 2012, at 5:14 PM, Peter Haworth <p...@lcsql.com> wrote:
> Unless I'm missing something, closing and removing a stack from memory does
> not trigger a closeStack message. That seems really strange to me but be
> that as it may, is there some other message that can be used to trap when
> that happens?
> Pete
> lcSQL Software <http://www.lcsql.com>
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
