This might seem silly to ask now, but... what exactly is sysfs? I tried to look for it online, and all I managed to understand is that it's a virtual filesystem. What exactly does it do, and how do we use it?Favux wrote: Right. And sanette did some refinements to Karg's user land OLED app. All that's on the Intuos4 OLED thread: http://ubuntuforums.org/showthread.php?t=1380744 But having to remove the wacom.ko (usb kernel driver) module and restore it is why Eduardo Hasenleithner came up with the sysfs approach in the kernel. Actually he started with something different and the kernel maintainer suggested using sysfs instead.
On the same note, I tried using your script. It created an empty file on my home folder called "3". I have no idea why. It also said that "0" is an unexpected operator and refused to work, and I'm really not sure why, as it doesn't seem too differently built from my own script.
There is one thing, though: the part:
Code: Select all
if [ $[MODE + 1] > 3 ]; then echo 0 > /tmp/mode_state else echo $[MODE + 1] > /tmp/mode_state fi
I looked for the status_led0_select file and found two which could be fitting, however I couldn't edit any one of them, not even with sudo, and I couldn't open them with a text editor.
So I'm absolutely baffled now.
Well, it's kinda hard to describe, but basically, what happens is that you use the same button names to point to which button you want to assign the keys, i.e., the middle button remains button 1, the bottom button is button 2, etc., but you can use the parameters 1, 2, 3, etc., to assign behaviors of those buttons, numbered from top to bottom.Favux wrote: This totally mystifies me. Sounds like something is being reset and I don't understand the button 5. According to my BambooPT HOW TO notes I guess that would be vertical scroll down wih 4 scroll up. Why can't you just use 5? But the key thing is you've shown the Wacom drivers are disabling the indended mode selection action of Button 1, i.e. the button in the center of the touch ring. To me that appears to be a bug the dev.s need to address. Of course there may be some way to handle it already and I am ignorant of it. You know, the kind of thing if you can just read through the C code is obvious.
For example, if my top button is configured to toggle touch capabalities, and I want to assign it to the fourth-to-top button (for whatever reason), I can do the following:
Code: Select all
xsetwacom set "Wacom Intuos5 touch M Pen pad Button 10 1
It's not scroll down. Rather, setting the parameter "button 5" isn't setting it to the X button 5, but to the tablet's fifth-to-top button.Favux wrote: If scroll down makes Button 1 go through modes I don't see why that would mess with assigning vertical scroll to other buttons. Strange.
And me. This is really a very positive experience for me, as I'm quite a beginner in Linux (I've been using it for around a year and am still finding it difficult at some points).Favux wrote: I think so too. This is fun. You're the first who's really been interested in exploring this so I'm learning a lot.