Navigation Perplexity

J. Landman Gay jacque at
Sun Mar 22 14:03:16 EDT 2009

dunbarx wrote:
> 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.

Makes sense. The handler runs to completion before it processes any 
mouse clicks. So it waits (during which you click B), then goes to stack 
A (which it is already on) and then notices you clicked and goes to B.

> 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".

Same deal I think. The last click won't get processed until after the 
mouseUp finishes.

Jacqueline Landman Gay         |     jacque at
HyperActive Software           |

More information about the Use-livecode mailing list