Hi. 2011/7/7 Peter Hutterer <[email protected]>: > On Wed, Jul 06, 2011 at 10:36:22PM +1200, Jason alavaliant wrote: >> On Wed, Jul 6, 2011 at 12:37 PM, Chris Bagwell <[email protected]> wrote: >> > I do not know the long term plan for this as well but I can make some >> > educated guesses. It doesn't make sense to use xsetwacom for this >> > feature unless you add logic directly into xf86-input-wacom that opens >> > the sysfs file and send data itself. If this is done then it will be >> > able to open that device for same reason it can open the root owned >> > /dev/input devices related to tablet. That would solve your problem >> > right there. >> > >> >> That seems a sensible way to cover it, didn't think of it going via the >> actual X driver rather than xsetwacom accessing sysfs directly. > > I suggest to add a property containing a number of Pixmaps (in the order of > the oleds on > the device) and the Pixmaps contain the actual data. The conversion between > Pixmap to driver-specific data format is then done in the driver. > Pixmaps are just 32 bit IDs, so the property code is trivial too. > > This way you get to use all client-side tools that already draw to pixmaps > (e.g. cairo) instead of having to write your own.
Using xsetwacom was and is still my plan to get OLED control. The work of integrating it into xf86-input-wacom has fallen asleep a bit, but I hope the kernel patch will be accepted soon, so I can proceed with the development. Eduard ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
