On Wed, Jul 17, 2013 at 9:18 PM, Isaac <ozixtheora...@gmail.com> wrote:
> On Tue 16 Jul 2013 10:27:08 PM MDT, Isaac wrote:
> > On Mon 15 Jul 2013 10:18:09 PM MDT, Isaac wrote:
> >> On Mon 15 Jul 2013 04:43:06 AM MDT, Przemo Firszt wrote:
> >>>
> >>> Dnia 13 Lipca 2013, 08:00, So, Bastien Nocera napisał(a):
> >>>> Em Fri, 2013-07-12 Ă s 20:08 -0600, Isaac Nygaard escreveu:
> >>>>> Hello all,
> >>>>>
> >>>>> I have been looking for a way to set the LED lights for an Intuos 4
> >>>>> using C/C++. I found the "i4oled" project here, but can't find any
> >>>>> way
> >>>>> to change the LED lights associated with the touch ring. I would like
> >>>>> to write a program that can cycle through four different touch ring
> >>>>> modes.
> >>>>
> >>>> That's something that's integrated in gnome-settings-daemon, thus
> >>>> GNOME
> >>>> itself.
> >>> i4oled is for OLEDs only. If you want to access the leds/oleds directly
> >>> you have to use kernel sysfs. More info here:
> >>>
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/ABI/testing/sysfs-driver-wacom
> >>>
> >>>
> >>>
> >>
> >> Thanks a lot. I'll check these out.
> >
> > I am able to change the led lights through sysfs writes. However, it
> > requires the script to run as root, which is fine; though, it would be
> > nice if there were a way to do this without asking for the user's
> > password. Is there any good ways to work around this?
>
> Another question: is there any way to have the tablet buttons
> run/communicate to another program? The documentation only mentions
> mapping the buttons to X input keys.
>
>
If you are trying to pipe the buttons into an existing program, you can use
something like xsetwacom or the GNOME control center to map the buttons to
specific mouse buttons or keyboard keys. If you're writing the program that
needs to use the buttons, the easiest thing to do is to act upon mouse
button events (note that tablet's buttons skip over mouse buttons 4-7 by
default, and that GNOME intercepts all these events by default). If you're
writing a program that won't be running under X, you may need to read the
kernel events directly from /dev/input/eventN (read up on the documentation
at [1], [2], and [3]).
[1]: https://www.kernel.org/doc/Documentation/input/input.txt
[2]: https://www.kernel.org/doc/Documentation/input/input-programming.txt
[3]: https://www.kernel.org/doc/Documentation/input/event-codes.txt
Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
