On Tue, Aug 16, 2011 at 04:02:15PM -0700, Ping Cheng wrote:
> 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?
>From the server source code:
#define MAX_VALUATORS 36
can't remember if that's arbitrary or due to the libXi implementation for
inputproto 1.x but either way, we have enough valuators that we can add
another one. I vaguely recall Alexia talking about some GIMP limitations for
more than 6 valuators though.
> 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).
ABS_VOLUME for a LED???
> 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.
what does it do?
Cheers,
Peter
------------------------------------------------------------------------------
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
