Updating stack without going to it

[Jim Ault]

I don't have time to investigate your setup, however I can answer the export
question: 

> This is confirmed in the message watcher (and by the way, how do you
> export its contents?).
open the message watcher, then do
put the stacks 
into the msg box, hit enter
in the list of stacks should be

/Applications/Revolution Enterprise/2.7.2-gm-1/Toolset/
revmessagewatcher.rev
thus.. in the msg box
put the number of fields in card 1 of stack " revmessagewatcher.rev"
-> 5
put  field 1 of card 1 of stack "revmessagewatcher"
->bingo... this is what you want.
----------------------------
You might want to watch for multiple resumeStack messages when

go stack "the main one" is executed
.. and which resume stack is being trapped
.. and which comes first.. suspend, resume, ??
.. does this work as expected when you toggle slowly?


Jim Ault
Las Vegas


On 11/8/07 7:49 PM, "Mark Swindell" <mdswindell at cruzio.com> wrote:

> Thanks Jim and Ian.
> 
> Maybe I've got a handle on the recursion, I don't know.
> 
> But maybe you or others can explain the following.  I simplified my
> setup and recreated the following scenario:
> 
> A main stack with a field, and two substacks: FirstSub, SecondSub
> 
> At the stack level in the main stack ("The Main One") I have this
> script:
> on updateNavCard
>      go stack "the main one"
>      put "hello"&return after field 1
> end updateNavCard
> 
> At the stack level of each of the sub stacks I have this:
> on resumeStack
>      updateNavCard
> end resumeStack
> 
> Now I toggle back and forth between the two substack windows.
> First two toggles a suspendstack and resumestack is sent and hello
> appears.
> Next two toggles only a suspendstack is sent and no "hello" appears.
> Then two more "hellos"
> Then two no hellos.
> And so on.
> 
> This is confirmed in the message watcher (and by the way, how do you
> export its contents?).
>