what about using the xinput interface? this is the way x programs normally deal with having extra input devices that different programs interpret in different ways.
pix.
On Tue, 8 Apr 2003 16:12:48 +0200 Christian Klippel ck@mamalala.de wrote:
hi,
Am Dienstag, 8. April 2003 15:20 schrieb Hans-Christoph Steiner:
I am currently working on a Pd_linux object called [rawmouse] which reads info direct from the Linux event interface. Once its done, it should be trivial to make a [rawtablet] object. But its not done yet...
.hc
if you read the event device, you can make a general purpose object. just read the event, and give it to either seperate outlets (type,code,value1,value2) or as list on a single outlet. there is an timestamp in the event message also, if needed, that could be given an outlet.....
that way it can be used with any event device, mice, tablets, joysticks,
pens... its then just up to the patch to decode the needed events. one can make simple patches for a ready-to-use mouse decoder based on that, for example.
greets,
chris
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list