On 22/01/16 23:00, Richmond wrote:
On 22/01/16 20:46, John Dixon wrote:
look harder...
mouse([buttonNumber])
the mouse
from the dictionary...
So, I made a wee stack containing a field: fld "MB"
and put this in the cardScript:
on mouseDown
if mouse(1) is "down" then
put 1 into f
On 22/01/16 20:46, John Dixon wrote:
look harder...
mouse([buttonNumber])
the mouse
from the dictionary...
So, I made a wee stack containing a field: fld "MB"
and put this in the cardScript:
on mouseDown
if mouse(1) is "down" then
put 1 into fld "MB"
end if
if mouse(2) is
On 22/01/16 20:46, John Dixon wrote:
look harder...
mouse([buttonNumber])
the mouse
from the dictionary...
I did and gottit. Thanks.
Richmond.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsub
On 2016-01-22 19:01, Matt Maier wrote:
I used mouse() in code that I've only personally run on my Windows
machine.
My friend ran the same code on Ubuntu and we found that mouse() is off
by 1.
So on Windows mouse(1,2,3) correspond to the left, middle, and right
mouse
buttons. But on Ubuntu th
look harder...
mouse([buttonNumber])
the mouse
from the dictionary...
> Subject: Re: mouse button
> To: use-livecode@lists.runrev.com
> From: richmondmathew...@gmail.com
> Date: Fri, 22 Jan 2016 20:37:04 +0200
>
> On 22/01/16 20:01, Matt Maier wrote:
> > I used m
On 22/01/16 20:01, Matt Maier wrote:
I used mouse() in code that I've only personally run on my Windows machine.
My friend ran the same code on Ubuntu and we found that mouse() is off by 1.
So on Windows mouse(1,2,3) correspond to the left, middle, and right mouse
buttons. But on Ubuntu the same
I used mouse() in code that I've only personally run on my Windows machine.
My friend ran the same code on Ubuntu and we found that mouse() is off by 1.
So on Windows mouse(1,2,3) correspond to the left, middle, and right mouse
buttons. But on Ubuntu the same buttons are mouse(0,1,2).
Is that how
