On 02/18/12 20:36, Hans-Christoph Steiner wrote:
[hid] on Linux relies on a /dev/input/event* devices. If that device does not
provide a /dev/input/event* device, then [hid] can't read it. One possibility
is that you are using an X driver for that tablet, so not a /dev/input/event*
device.
Hello,
I used the last input-wacom driver :
insmod /home/.../input-wacom-0.12.1/2.6.30/wacom.ko
When loaded it creates /dev/input/event14 and a /dev/input/wacom entries
I ran pd with sudo.
I tested the HID object with the example of the documentation. The
info message displayed correctly the
I believe that X11 gets locks access to the device exclusively. This affects
all devices. Search puredata.info and the archives of this list for notes on
how to get around this.
.hc
On Feb 19, 2012, at 2:22 PM, Sylvain Hanneton wrote:
Hello,
I used the last input-wacom driver :
insmod
Hello,
I try to capture the data from my Bamboo touch wacom tablet with the HID
object.
Everything is ok except the polling of the data.
The tablet works fine with X. I can see the data with the xidump command
line tool.
I think that the input events are provided only to the X event queue
[hid] on Linux relies on a /dev/input/event* devices. If that device does not
provide a /dev/input/event* device, then [hid] can't read it. One possibility
is that you are using an X driver for that tablet, so not a /dev/input/event*
device.
.hc
On Feb 18, 2012, at 8:34 AM, Sylvain
