nanogui: Thread: buttons

Currently Nano-X and Microwindows support three mouse buttons,
LBUTTON, MBUTTON, RBUTTON.  IIRC, X supports up to five buttons (1-5),
and those funky intellimouse things (aka wheel mouse) can generate all
5.  Should we switch over?  

There obviously aren't any applications for mwin or nanox that use
these things, but we might want to switch to numbered buttons (instead
of L,M,&R) now, when there's less apps to break.  

Unless L,M,&R is better for micros~1 compat.  I dunno about this.  If
no objections, I'll work up a patch.

-- 
      You're just jealous because the voices only talk to me.

Daniel Risacher                                   ####@####.####

: Currently Nano-X and Microwindows support three mouse buttons,
: LBUTTON, MBUTTON, RBUTTON.  IIRC, X supports up to five buttons (1-5),
: and those funky intellimouse things (aka wheel mouse) can generate all
: 5.  Should we switch over?

I definitely don't think so.  I changed nano-X some months ago from numbered
buttons to letters, because the different applications didn't agree on the
functionality
of the buttons.  Some apps used 1, some 3, when they both meant left.

In regards to supporting more mice features, I'd suggest that if you want
to add that stuff, start by enhancing the mouse drivers to support that feature,
and then add a functionality-labeled define, rather than a numbered define.

Doing it this way allows mid level routines to add functionality to, say,
slider controls because they know the functionality, and there isn't any
argument over the button "number".  For instance, if a BUTTON_WHEEL
event is received, a custom control can scroll the scroll bar, rather than
hoping that button 3, or is it 5, is the wheel.

Regards,

Greg

> I definitely don't think so.  I changed nano-X some months ago from numbered
> buttons to letters, because the different applications didn't agree on the
> functionality
> of the buttons.  Some apps used 1, some 3, when they both meant left.

That can be a bad thing in some ways because left handed users want to swap
them over. At first glance you might think you can just hide it in the mouse
driver, however there is a small matter of getting help texts right for both
cases 8(.

Having the mouse buttons labelled is ok, providing the mouse driver can be
asked very simply for a current mapping

Some apps used 1, some 3, when they both meant left.
:
: That can be a bad thing in some ways because left handed users want to swap
: them over. At first glance you might think you can just hide it in the mouse
: driver, however there is a small matter of getting help texts right for both
: cases 8(.
:
: Having the mouse buttons labelled is ok, providing the mouse driver can be
: asked very simply for a current mapping

The way I like to handle this case is by having a single way to tell the system
to "swap buttons for a left handed user".  In that case, the implementation does
whatever is required to make things work as expected for the lefty...
Applications
don't get into the business of handling leftedness, and everything works without
much complication.

Regards,

Greg