I think I figured it out. Thanks for the ideas about troubleshooting but
none of those rabbit holes were particularly informative.
Eventually while doing something else I went back through the dictionary
entries for the various commands that make use of external stacks. It
finally dawned on me tha
the executionContexts
Bob S
On Apr 4, 2017, at 19:22 , Matt Maier via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
I'm not aware of a way to "trace" where a message has been and the keywords
I can think of aren't turning up anything promising in the dictionary or
google.
_
Place a breakpoint in the closeStack handler. When it fires and the
script goes into debug mode, look at the popdown menu button just to the
right of the debugging icons at the top left of the script window.
That's the execution contexts, and it tells you what path the message
took. The top lin
raig
>
>
>
>
> -Original Message-
> From: Matt Maier via use-livecode
> To: How to use LiveCode
> Cc: Matt Maier
> Sent: Tue, Apr 4, 2017 10:23 pm
> Subject: Re: this stack gets every closeStack message
>
> I'm not aware of a way to "trace&quo
, Apr 4, 2017 10:23 pm
Subject: Re: this stack gets every closeStack message
I'm not aware of a way to "trace" where a message has been and the keywords
I can think of aren't turning up anything promising in the dictionary or
google.
On Tue, Apr 4, 2017 at 6:10 PM, dunbarx vi
ou send a "closeStack" message from your "lower" stack and trace it?
>
> Craig Newman
>
>
>
> --
> View this message in context: http://runtime-revolution.
> 278305.n4.nabble.com/this-stack-gets-every-closeStack-
>
quot;closeStack" message from your "lower" stack and trace it?
Craig Newman
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/this-stack-gets-every-closeStack-message-tp4713692p4713694.html
Sent from the Revolution - User mail
So I've got a mainstack (#1). It calls a different mainstack (#2) so that I
can save data like API keys in #2 stack before closing it.
When I'm in the IDE #2 stack is getting and responding to every single
closeStack message that happens, including when I close IDE windows (ex:
script editor, vari
