Actually it was the other way round. I never enabled this special typographic keyboard layout. That is, not that I remember. I might have tried it once, and didn't notice that I wasn't able to turn...
Type: Posts; User: dr4ziw; Keyword(s):
Actually it was the other way round. I never enabled this special typographic keyboard layout. That is, not that I remember. I might have tried it once, and didn't notice that I wasn't able to turn...
Hi, Nicolas!
Good to see that I'm not the only one to experience this problem. And I'm very glad that my solution helped.
Concerning "misc:typo"…
I'm not entirely sure, but AFAIK that switch...
To set that straight, I don't get any response from touch either, except for with synclient -m.
But, that's what I had with the Lucid default synaptics package. Only difference I can see is that...
Favux, I think I need your opinion here.
Still trying to get touch on the synaptics driver, is it enough if the driver catches "/dev/input/event*", or does it also have to get hold of...
Hi, SOG420
Any reason why you're using xorg.conf, instead of 10-wacom.conf (via xorg.conf.d)? Makes life a little easier, xorg.conf a little lighter, and (most important) allows for hotplugging ;)
...
Hi, Favux.
Didn't until now.
For the moment, I merely moved 10-wacom.conf out of /usr/lib/X11/xorg.conf.d.
What happens is, evdev catches the tablet (pen) -- as it should, I suppose....
Update:
Played around a bit...
Although, I can't get the pointer to follow touch, can't get pressure or finger width information to the synclient, I meanwhile know what the four pad buttons are...
... furthermore, synclient does report that it's receiving position data (x,y) from the tablet. Pressure (z) stays at zero, while # of fingers (f) is usually "2" when I touch the tablet, and "0" when...
Hi, Favux.
Those videos look... to be honest, I don't like the idea of controlling a computer with touchscreen. Call me old fashioned, but if anybody were to touch my monitor he'd need an arm...
Favux, could you elaborate a bit more on this?
When you say that you want to put touch on the synaptic driver, you mean instead of the wacom driver? So, the touch part of the Bamboo would function...
cheshirekow, did you configure the pad buttons at all, e.g. with the example .xsetwacom.sh script you can find in the very first posting of this thread?
(very likely you'd have to change the device...
Oops! Sorry ;)
The latest linuxwacom-announce says 0xD6 and 0xD7 were added ... 0xDA (and a few others) were obviously added a while before.
Should give the developers a little rest before Wacom...
Hi, andreschandia.
Looks like you're running with an older wacom.ko version, which didn't include you're tablet.
Download the latest input-wacom-0.10.10-1 from here:...
0.8.8-10 provides you with the stable kernel module, while -- as far as I know -- input-wacom-0.10.10 is more experimental.
As for the tablet no longer working with newer kernel versions... Did...
You're welcome.
I think with the Maverick kernel (2.6.35) that's the best you can get. At least, that's how touch is working here as well. For better multitouch gestures we'll have to wait for...
Ah, on page 37 it was.
wcmValidateDevice.c needed to be patched to recognize newer tablets -- back then it was the Bamboo Comic one.
Chances are good that adding
case 0xD8: ...
To execute ~/.xsetwacom.sh automatically you first have to
chmod +x .xsetwacom.sh
in your home directory.
Then add
sh $HOME/.xsetwacom.sh
to your startup programs in System/Settings --...
Couldn't wait, so I applied the patch right away. Doesn't change anything, unfortunately.
At least not to the naked eye.
In order to get smooth pixel by pixel movement, I still have to lower...
Wow! You've really been busy.
Also read your posting on linuxwacom-discuss.
As Alexia correctly points out, Hardy had Gimp 2.4...
Installing Gimp 2.6 for Ubuntu 8.04 from GetDeb would be an...
Exactly! Leaving it commented out and put a warning there, that guidelines very likely won't work anymore if uncommented, would be the safest way to go.
I think, I only have to use sthree modifier...
That it might happen? Sounds good.
I think the safest way would be to leave the 'Mode absolute' lines inside the script, but leave them commented out -- maybe already as 'Mode relative', so...
Top left corner... Tried that already and never could get a guideline out of there.
For the moment, I'll stick with placing guidelines with the mouse. And as long as the mouse is working... It's...
Okay, if I set the mouse to screen, I can draw, select, crop, etc. However, I can't drag out guidelines.
On the other hand, when I don't touch "xsetwacom set ID Mode absolute" for stylus and...
Sorry to interrupt.
@Favux: Concerning your proposed .xsetwacom.sh: Looks okay to me -- you've only replaced ClickForce with the new Threshold, haven't you?
Only thing which bugs me a little......
You're welcome.
Meanwhile, I know why simply moving the pointer often gets interpreted as a 1FG double tap:
Increasing the TapTime to 500ms was not a great idea. Every second contact within that...