> > Hi, > > I have some keys on my notebook which don't deliver scancodes, a kernel > driver provides a device to access those keys. > I started writing a XInput keyboard driver, which reads this device and > sends key events using xf86PostKeyEvent. > As I tried xev on it, I saw no events showing up. I then found the tool > xinput and using it I finally got the events I wanted to see. > Digging through the sources I found out that XInput devices produce > different events which you must first select to receive them in your > application. I also found that with xf86PostButtonEvent and > xf86PostMotionEvent it is possible to generate core events instead. > > I patched xf86Xinput.c to allow the sending of core events and it worked > perfectly, my events showed up like normal key presses. > > Why is there no such possibility in xf86PostKeyEvent? >
Most likely because you are the first one to need it. The core event feature of the mouse/touchscreen/tablet drivers is an XFree86 addition. The XInput SI code has no concept of a secondary device also sending core events. It only has the notion that 1 device is the core, but which one it is can be switched programmatically. In practice, that turns out not to be an adequate model, so the SendCoreEvents feature was added. But I'm not aware of anyone having worked with secondary keyboard devices before, so it was not added to that code path. -- Chris Bare Metro Link Incorporated [EMAIL PROTECTED] http://www.metrolink.com/ _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
