On Apr 30, 2009, at 6:53 AM, Tom wrote:
Charles Yeomans wrote:
The behavior as you see it has been so as long as I can remember.
But the documentation for the current version of REALbasic states
"The mouse button was released inside the Canvas region at the
location passed in to x,y"
I suggest that you file a feedback report.
Thanks for the info. I wrote a bug report abut this.
I understand the the MouseUp outside of the canvas is helpful for
drag & drop but for a custom button it makes more work because you
need to check the x/y-position of the MouseUp event.
Perhaps it would be helpful to make the behavior optional...
I also feel that we should get a MouseExit event if the mouse is
moved out of the canvas while the button is down. That would make
tracking this situation even easier. I know this was requested back
in the old bug database, but the Carbon blocking event model on
MouseDown prevented it from being instituted.
I've always used the X/Y check in the MouseUp event to make sure the
event occurred within the Canvas.
If X > Me.Left And (X < Me.Left + Me.Width) And Y > Me.Top And (Y <
Me.Top + Me.Height) Then
// do mouseup action
End If
Tim
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|