[Use-revolution] RE: Constraining Movement

Chipp Walters chipp at chipp.com
Tue Nov 27 21:30:21 EST 2001


Thanks for that bit of clarity. As I recall (years ago) we used a mouseLeave
in SC to do a similar thing...but not exactly the same.

chipp

-----Original Message-----
From: use-revolution-errors at www.runrev.com
[mailto:use-revolution-errors at www.runrev.com]On Behalf Of Scott Rossi
Sent: Tuesday, November 27, 2001 2:49 PM
To: use-revolution at www.runrev.com
Subject: Re: Constraining Movement


Recently, Chipp Walters wrote:

> why do you need the mouseRelease handler? Just wondering.

Because a mouseUp message is only sent when the mouse is directly over the
clicked control.  If the user drags their mouse outside the stack for
example, there is no way to pass mouseUp to the clicked control and
therefore no way to stop the dragging action.  MouseRelease is key in this
situation.

Regards,

Scott

_____________________________________________________________________
Scott Rossi                       Tactile Media - Multimedia & Design
Creative Director                 Email: scott at tactilemedia.com
                                  Web: www.tactilemedia.com




More information about the use-livecode mailing list