Updating stack without going to it

Jim Ault JimAultWins at yahoo.com
Fri Nov 9 00:04:32 EST 2007


You could make a slight change

> on resumeStack
      updateNavCard (the short name of this stack)
> end resumeStack


 on updateNavCard sourceOfMsg
>      go stack "the main one"
      put "hello"&& sourceOfMsg  & return after field 1
> end updateNavCard

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?).
> 
> Why isn't a resume stack sent each time?
> 





More information about the Use-livecode mailing list