Navigation Perplexity

stephen barncard stephenREVOLUTION2 at
Sun Mar 22 00:59:19 EDT 2009

You owe it to yourself to check out Dar Scott's tutorials, including
'Message Mechanics' which can graphically illustrate how Rev's messaging

Stephen Barncard
San Francisco

2009/3/21 dunbarx <dunbarx at>

> Reposting this:
> I thought I knew how these things worked. Even HC does this, I just found
> out.
> Two stacks, "A" and "B". In a button handler on "A":
> on mouseUp
>   wait 200
>   go stack "A" -- remember, the button is in "A"
> end mouseUp
> During the wait period, if I click anywhere on stack "B", the frontmost
> stack
> is "B" after the timeout. If, instead of "wait", I have a repeat loop
> that allows me time to click on stack "B" before it terminates, I still am
> left in
> "B". The click's loc is remembered with a vengeance, overRiding the "go"
> command,
> far more than I would have thought possible.
> Pushing/Popping cards, going to "A" five times, nothing matters.
> It's like I am 1 hour into HC in '87. I can't believe I never noticed
> before.
> This isn't even a Rev thing.
> Craig Newman
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the Use-livecode mailing list