RC1 issue with mouse() function

Sarah sarahr at genesearch.com.au
Fri May 23 02:12:00 EDT 2003

Confirmed: I am using a three button mouse with Mac OS X and all three 
buttons produced down for all three mouse(x) tests. I didn't use your 
function, I had a message that checked each and set the hilite of a 
checkbox (just in case the mouseDown trigger was messing things up, but 
I still got either all three checkboxes checked or unchecked, never one 
at a time as I would have expected.

Rev obviously detected the various mouse buttons (at least 1 & 3) but 
there must be something odd about the mouse() function.


On Friday, May 23, 2003, at 03:28  pm, MacGuy wrote:

> Can anyone confirm if this is a bug, or perhap-s an issue on my end?  
> I find that the mouse() function returns true no matter which 
> "mouseButton" is pressed.
> I'm using Mac OS X 10.2.3 and RC1.  A simple mouse click should be the 
> equiv of mouse(1), however the following script:
> on mouseDown
>   put (mouse(1) is "down") & comma \
>   & (mouse(2) is "down") & comma \
>   & (mouse(3) is "down")
> end mouseDown
> returns: true,true,true
> the ctrlKey was not down (for a mouse(3) to be true under Mac OS), 
> this was just a mousedown
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution

More information about the use-livecode mailing list