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
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 via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Two independent stacks are at the same "l
Two independent stacks are at the same "level" in the hierarchy. Unless one
is put into use or otherwise explicitly made to trap messages above another
stack (like inserting a stack script into back, for example), I am not sure
how you are seeing what you are seeing.
Can you send a "closeStack" me
