[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mouse button handling

From: Thomas Dickey
Subject: Re: Mouse button handling
Date: Thu, 15 Sep 2011 19:31:12 -0400 (EDT)

On Fri, 16 Sep 2011, Anders Juel Jensen wrote:

With Damien's patch i get a much more responsive interaction - as in,
now mouse-clicks aren't vanishing into thin air.

That being said, I still get some funny behavior, like getting
BUTTON1_CLICKED despite only having set mousemask to the PRESSED
and RELEASED variants.  Attached is my small test program. Sorry for
the use of panels, but for mysterious reasons I can't get screen output
without (?!?). It should at least illustrate the _CLICKED problem, and
if you are lucky enough you might also see a "We got KEY_MOUSE but there
was no pending event?!?". That one is pretty hard to reproduce - but
I have gotten it twice while doing heavy mouse workout :P
Oh, and I to get movements for scroll, and nowhere else.

Also I seem incapable of setting up an xterm
correctly for mouse position reporting... I tried "xterm -tn
xterm-1003" with no luck, so I figure I'd better go investigate, and lo
and behold, running infocmp on both xterm and xterm-1003 showed no
difference.. err.. this is wrong, right?


        infocmp -x xterm xterm-1003

xterm-1002 and xterm-1003 use a mode added to xterm which allows it to
report events as you move the mouse around (one does this only when the
button-1 is pressed, while the other always does it).  Unlike the wheel
mouse (buttons 4 _and_ 5) this should work whether or not the extended
mouse feature is enabled.

ncurses looks at the kmous and XM capabilities (the latter is an extension, mentioned in the curs_mouse manpage).

I don't see any particular problem with the configure options (but am
busy on another program - I generally work on ncurses on Saturdays).

Thomas E. Dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]