Hello, I'm new here. And I wonder, why didn't I get ALL the buttons on
my mouse in a 'button tester' program.
In Qt, I have been responsible for extending the range of valid mouse
buttons from a longstanding limit of 5 buttons. The enhancement to the
DirectFB "plugin" code, in Qt Version 5.0, is all done. (And so are xcb,
xlib, wayland, and generic/edvdev). But my Qt "buttontester" Qt doesn't
seem to send any more than 3 mouse buttons under DirectFB, even when the
mouse has been configured as a udev/evdev Linux device. Let me summarize
the log messages which I saw during that test:
(A) In my .directfbrc, I specified Linux Input for my evdev mouse, with
the proper event number.
(B) I run the program, and the relevant console messages ("behind" the
GUI Window) appear in this order:
#1, a udev device is "seen", assigned to Linux-input. (good).
#2, Linux-Input correctly identifies the Logitech USB Receiver. (good.)
--> it seems to break here <--
#3, a message about the secondary device being initialized, under
emulation, as a 3-button serial mouse. (A PS/2, IIRC. Not Good, that's a
brain-damaged device!)
and then:
#4 All Button with identifiers higher than "middle button" behave as
lower-numbered buttons (as if it were a 3-button, vertical wheel PS/2
serial device.)
- - - - -
'man directfbrc' shows several choices for mouse, but I had hoped that
they would NOT interfere with Linux-Input devices under the evdev
module. (I'm referring to the kernel module-- I did not have X11
running). In any case, I get only 3 button numbers. The Qt code is very
straightforward, and the button tester runs fine on all of the other
platforms. This leads to some questions:
(1) Did I fail to provide some necessary specification in .directfbrc,
OTHER THAN listing my mouse device event# as a linux-input device?
(2) If not, do we want to add another value into set of valid protocols
for 'mouse-protocol'?
BTW, we should probably use a new value, so that a configuration file
which DOESN'T specify the new value (e.g. "mouse-protocol=evdev") will
stay with the current, "dumb PS/2" behavior. Or, perhaps, DirectFB users
don't have much use for "gamer mice" with DirectFB programs?
Please advise. I could hack at it, but, having never used DirectFB, --
it would take me longer, and I'd be more prone to miss things, than some
of you.
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
