Hi.
Wait commands are blocking. They should only be used when it is your intention to force the user to take an action in a certain way. or to delay the entire system for some purpose. An "answer" dialog is one example of this sort of thing. It is a blocking process, and the only thing you can do is to click one of the buttons on it. Another example is this, in a button script:
Code: Select all
on mouseUp
wait 20
if the mouseClick then answer "two" else answer "one"
end mouseUp
Here we have a wait command, and the only thing that can happen during its interval is that the user might or might not click the mouse within that time period. It is a way to detect double-clicks.
When you have more than one possible user path, (as you say, the user might want to navigate to another card instead of performing the action the wait command has presented) then you need to change the way you are working your interface. Sometimes it is far better to take a different route than to try to maneuver around an existing troublesome situation.
Or am I missing your point?
Craig
)