The "move" command seems to be blocking, except when another "move" command is sent. But that is not the issue.
In a new card make three buttons. Name them "player", "stop" and "go". In the script of the card AND the "go" button:
Code: Select all
on mouseUp
put "go"
move button"player" to the clickLoc in 3 seconds
end mouseUp
Code: Select all
on mouseUp
put "stop"
stop moving btn "player"
end mouseUp
Click the "go" button. Now the "stop moving" command works like it should by clicking on the "stop" button.
So.
Why, if the "move" command is in the card script, is the handler in the "stop" button ignored? More than that. WHY, during a move, can a new move be invoked right through the "stop" button as if it were not there at all, as if the user clicked on blank space on an open card???? This actually is the case with any object, even if it has a "mouseUp" handler in its script. Any click passes right through during a move event.
As a side note, is there no way to "move with messages"? Only the "stop moving" command (of course, when not invoked if the "start moving" originated in the card script) seems to be able to "interrupt" the motion.
I cannot wait to hear what simple solution there is to that last. But I am perplexed by the first issue.
Craig Newman