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
I thought that, too. I don't know why my whole life I believed that the event
queue was suspended during wait.
It certainly makes sense, in hindsight, that a repeat loop would work that way.
Sorry I mentioned it. After all, I have interrogated the mouse during loops as
a matter of course. Who
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
You owe it to yourself to check out Dar Scott's tutorials, including
'Message Mechanics' which can graphically illustrate how Rev's messaging
works.
http://pages.swcp.com/dsc/revstacks.html
Stephen Barncard
-
San Francisco
http://barncard.com
2009/3/21 dunbarx
