Dear Experts, I have a slightly unusual wireless mouse with 6 buttons. 3 are the normal mouse buttons and work correctly, while the other 3 behave like keyboard keys F13 to F15. So far I have failed to get DirectFB to recognise these extra buttons.
I have looked at the raw data from /dev/input/event1 and I can see events of type EV_KEY and code KEY_F13 to KEY_F15 when these buttons are pressed. I also see normal mouse motion and button press events there. When my program starts it uses EnumInputDevices to find this mouse; it then associates an event buffer with it and waits for events. Using strace I can see that it reads data from /dev/input/event1 including both the F13...F15 keypresses and the normal mouse events. However, the keypresses do not seem to result in events in the event buffer. I have had a look at inputdrivers/linux_input/linux_input.c and F13 to F15 do seem to be included in the keycode translation logic, and I can't see anything else that would stop this from working. Am I doing something wrong, or is this something that's not expected to work? Can anyone suggest a debugging strategy? (I'm still using 0.9.25, if that makes any difference.) Many thanks, Phil. _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
