Follow-up Comment #10, bug #17005 (project mypaint):
Yeah, it is a pretty bad hack, but so is Gtk guessing by name when XInput
makes the information available. I looked around and, unfortunately, calling
the xsetwacom or xinput commands with a subprocess seems to be the primary way
of doing it "right", at least with Python and some other languages, because
Gtk can't be trusted to give accurate information. I figured using a
subprocess would be too hackish to be merged, but I still thought I should
try since it yields more accurate results than guesswork. :)
The xsetwacom source shows how it should really be done - by including
XInput.h and checking device properties - but that requires XInput bindings,
which Python seems to lack. If they were available it would avoid the
subprocess but that still seems kludgy because it's still bypassing Gtk for
something it should be dealing with for you.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?17005>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Mypaint-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/mypaint-bugs
