Thanks Terry,
I guess that means the saying "Trust but Verify" applies to the LR
A side observation. I put a line of code in the mouse enter and mouse
exit events to change the cursor when in the static text region. That
works fine. So I could set a "flag" true on mouse enter and False on
mouse exit and then check that flag in the mouse up event, but I
think I'll go with your if test.
Thanks Again
Lou
On Jan 20, 2007, at 5:22 AM, Terry Ford wrote:
On Jan 19, 2007, at 3:34 PM, Louis G5 Batayte wrote:
According to the Language Reference page on Static Text, the mouse
up should not fire unless the button was released inside the
statictext region. How far away from the static text do I have to
get to be outside the statictext region?
The only two controls (AFAIK) that will actually do this
automatically in their Action events are Pushbutton and
BevelButton. Even though they all say something similar to "The
mouse button was released inside the control's region at the
location passed in to x,y.", they are all wrong. Even those two
will respond outside their region if you put the code in their
Mouse events.
Don't you just love the LR's consistency. :-P
Actually it should probably be worded: "The MouseDown event was
pressed inside the controls region and Returned True. The location
passed in to x,y is where the Mouse was released relative to the
Top-Left edge of the control's region."; or something like that.
Fortunately there's a simple fix for the MouseUp event:
If x<0 or x>me.Width or y<0 or y>me.Height Then Return
-Terry
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
