I need to report a new value to the user-land for pad. We have the forth (left strip), fifth (right strip), and sixth (abs wheel) axises in use. The first three are unused because they are (kinda) reserved for X, Y, and pressure although pad has none of them. Now, I need to report a new value. If I use the sixth axis, we may have issue with wheels, which has a value of 0 - 71. I plan to reserve one byte (0 - 255) for the new value. Since we can inform X server that a tool (pad, that is) does not emit motion events, maybe we can reuse the first axis? Then, how do we resolve the backward compatibility issue?
I don't know what I can call the new value yet. It will need to get through the LKML's review when the kernel driver is ready. I am thinking to call it "ABS_VOLUME", which represents the led that is turned on (yeah, we are going to support LED in the driver). Another way to report this value is through "xsetwacom get pad ". It has less challenge to implement. But, is it a good solution? Please share your thoughts. Ping
------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
