Hi
As also reported in http://ubuntuforums.org/showthread.php?t=1120029
my Intuos4 L does not work properly on Ubuntu Lucid with a quite new
git version of the xf86-input-wacom. Only the left half of the tablet
is usable, if the stylus is moved to the right half it jumps to the
leftmost location.
On 2011-03-03 00:24, Pander wrote:
Hi all,
Here is version 2 of my toggle scripts with notification.
Now for the 100 virtual dollar question, how can I call then via my
tablet with:
- button 4 (or 8)
- CTRL + button 4 (or 8)
- ALT + button 4 (or 8)
Who can help me out to start a shell
Adds 5 parameter descriptions to the xsetwacom manual: Mode,
PressureCurve, Rotate, TabletPCButton, and Threshold.
Favux
From 94a49c70ab1ecad0edbc393ddca0765d5f32a5ae Mon Sep 17 00:00:00 2001
From: David Foley favux...@gmail.com
Date: Sun, 6 Mar 2011 14:23:11 -0600
Subject: [PATCH]
HI Ping,
It has been reported by others. The fix has been to go back to
xf86-input-wacom-0.10.8 in Lucid (2.6.32) or update to a release with
X server 1.9, i.e. Maverick (I think 1.8 would work too). The default
xf86-input-wacom in Lucid (10.04) is 0.10.5.
Favux
On Sun, Mar 6, 2011 at 3:30
2011/3/6 Ping Cheng pingli...@gmail.com:
Just as a note: I compiled xf86-input-wacom-0.10.8 which is the last
release before commit 19c24dc4e852bae384f16411d5f59add487be5f0 and it
appears to work correctly.
Oh, too bad. I wonder why the others have not seen the issue yet. Do you
have
On Mon, Mar 7, 2011 at 6:27 AM, Eduard Hasenleithner ehase...@gmail.comwrote:
2011/3/6 Ping Cheng pingli...@gmail.com:
Just as a note: I compiled xf86-input-wacom-0.10.8 which is the last
release before commit 19c24dc4e852bae384f16411d5f59add487be5f0 and it
appears to work correctly.
On Sun, Mar 06, 2011 at 03:00:38PM -0600, Favux ... wrote:
Adds 5 parameter descriptions to the xsetwacom manual: Mode,
PressureCurve, Rotate, TabletPCButton, and Threshold.
Favux
From 94a49c70ab1ecad0edbc393ddca0765d5f32a5ae Mon Sep 17 00:00:00 2001
From: David Foley favux...@gmail.com
On Fri, Mar 04, 2011 at 02:00:02PM -0600, Favux ... wrote:
Brings it into conformity with the 0xDA and makes it unique.
Favux
From 122cbe6c9abd657999db0151cb0ac045da8d0b63 Mon Sep 17 00:00:00 2001
From: David Foley favux...@gmail.com
Date: Fri, 4 Mar 2011 13:28:24 -0600
Subject: [PATCH]
On Fri, Mar 04, 2011 at 01:01:20PM -0600, Favux ... wrote:
From 6884bdf00857a93a1c56c74067d324fba73fde41 Mon Sep 17 00:00:00 2001
From: David Foley favux...@gmail.com
Date: Fri, 4 Mar 2011 12:50:39 -0600
Subject: [PATCH] conf: Add Fujitsu ISDV4 device ID FUJ02e9 to matches
Signed-off-by:
On Fri, Mar 04, 2011 at 12:39:52PM -0800, Ping Cheng wrote:
From: Andrzej Pronobis a.prono...@gmail.com
Signed-off-by: Ping Cheng pingli...@gmail.com
---
Hi Andrzej,
I changed your original patch a little and made it into git patch format.
If you agree with my changes, please reply to
On Sun, Mar 06, 2011 at 11:27:50PM +0100, Eduard Hasenleithner wrote:
2011/3/6 Ping Cheng pingli...@gmail.com:
Just as a note: I compiled xf86-input-wacom-0.10.8 which is the last
release before commit 19c24dc4e852bae384f16411d5f59add487be5f0 and it
appears to work correctly.
Oh, too
No functional change, making the code more readable.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
tools/xsetwacom.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/tools/xsetwacom.c b/tools/xsetwacom.c
index e606541..3b423f9 100644
---
xsetwacom set device Button 1 Ctrl Z cannot be parsed by xsetwacom,
leading to a nonfunctioning button without the user realising why. Print an
error and complain if the keyword is unknown/invalid.
Bug 3054502
https://sourceforge.net/tracker/?func=detailatid=525124aid=3054502group_id=69596
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
tools/xsetwacom.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/xsetwacom.c b/tools/xsetwacom.c
index 3b423f9..417e095 100644
--- a/tools/xsetwacom.c
+++ b/tools/xsetwacom.c
@@ -1283,9 +1283,9 @@ static
If keyword parsing failed and we have zero items to update to (but we're not
trying to reset the property), don't update the button action property.
Reproducer: xsetwacom set device Button 1 blah
would print an error about invalid keywords but still update (erase) the
button mapping property.
xsetwacom set devicename Button 1
should unsets the key action for button 1 (back to button mapping)
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
tools/xsetwacom.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/tools/xsetwacom.c
On Mon, Mar 7, 2011 at 7:57 AM, Peter Hutterer peter.hutte...@who-t.netwrote:
On Fri, Mar 04, 2011 at 12:39:52PM -0800, Ping Cheng wrote:
From: Andrzej Pronobis a.prono...@gmail.com
Signed-off-by: Ping Cheng pingli...@gmail.com
---
Hi Andrzej,
I changed your original patch a little
On Mon, Mar 07, 2011 at 02:47:37PM +0800, Ping Cheng wrote:
On Mon, Mar 7, 2011 at 7:57 AM, Peter Hutterer
peter.hutte...@who-t.netwrote:
On Fri, Mar 04, 2011 at 12:39:52PM -0800, Ping Cheng wrote:
From: Andrzej Pronobis a.prono...@gmail.com
Signed-off-by: Ping Cheng
On Mon, Mar 7, 2011 at 12:42 PM, Peter Hutterer peter.hutte...@who-t.netwrote:
xsetwacom set device Button 1 Ctrl Z cannot be parsed by xsetwacom,
leading to a nonfunctioning button without the user realising why. Print an
error and complain if the keyword is unknown/invalid.
Bug 3054502
19 matches
Mail list logo
