On Thu, 28 Feb 2002 Keelan Lightfoot <[EMAIL PROTECTED]> wrote:
>
> I found the cure for my problem script:
>
> on mousedown
> repeat until the mouse is up
> set the loc of me to the mouseloc
> end repeat
> end mousedown
>
> I can't use 'grab me', because in my actual code, there is code to make sure
> the object isn't dragged out of bounds, and to move selection handles with
> the object, etc.
>
> After fighting with it, I found that the way to stop the button from
> sticking to the finger after the mouse is up is to do this:
>
> on mousedown
> repeat until the mouse is up
> wait for messages
Very bad: you'll likely get recursion here because "wait for messages"
will actually cause a second mouseDown message to be delivered if the
user clicks during the following "set" command.
Note for RR doc people: "wait for messages" is an experts-only feature
that newbies should be strongly urged to not use. It's definitely a
"more than enough rope" kind of thing.
> set the loc of me to the mouseloc
> end repeat
> end mousedown
>
> It would seem that revolution doesn't recognize "until the mouse is up" as a
> queue to actually check to see if the mouse button has changed states during
> the loop.
Actually it works exactly the *opposite* of the way you describe.
Is anyone else struck by the irony of this post? Why do I waste my
time even trying to educate people on the issue when it's abundantly
clear that removing the mouse function from the language entirely is
only way to fix the problem...
Regards,
Scott
> - keelan
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
_______________________________________________
improve-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/improve-revolution
