Hi Peter,
Bisection shows it is the 12-21-10 Merge branch 'multimonitor-purge'
commit. Its snapshot xf86-input-wacom-68351da breaks touch. Although
rather than slamming to the left it jitters horizontally in place over
about 1.5 cm. The prior commit of the same date Bamboo tablet does
not
Hello,
thank you for this information, I'm looking forward to trying this out.
However, this does not adress my actual issue, which is, in an abstract
formulation
That I want to program the behaviour and the function of the keys.
But the only means to read from the device is through the emission
On Mon, Jan 10, 2011 at 09:16:14AM +1000, Peter Hutterer wrote:
On Sat, Jan 08, 2011 at 11:51:41AM +0100, Cedric Sodhi wrote:
I'm curious whether it would be possible and make sense to implement the
mode in which the pen could be read out so that it's proximity value
(which is currently in
Something about that bi-sect doesn't make sense. Your pointing to a
commit that contains no code.
I only have a few minutes with touch pad right now but tried git and
can also reproduce.
The only thing that looked suspicious in log files is this:
[1082669.808] (II) /dev/input/event6
Oh, if I do two finger touch, I'm able to get device type to change to
2 but I also get an additional interesting message (the last line in
this snippet):
[1084191.183] (II) /dev/input/event6 (10:wcmEvent): channel = 0
[1084191.183] (II) /dev/input/event6 (10:wcmEvent): c=0 i=3 t=2 s=1 x=9130
Hi Chris,
I'm pretty sure that's the right commit. But it was getting awfully late so...
Yes I'm testing input-wacom-0.10.10-1.
Favux
On Mon, Jan 10, 2011 at 8:48 AM, Chris Bagwell ch...@cnpbagwell.com wrote:
Oh, if I do two finger touch, I'm able to get device type to change to
2 but I
In reply to myself... oh yeah, the touchpad is a relative device. :-)
but maybe something in this area has changed slightly and needs a look
at. I'll try to dig deeper when I have a minute.
Chris
On Mon, Jan 10, 2011 at 8:48 AM, Chris Bagwell ch...@cnpbagwell.com wrote:
Oh, if I do two finger
Hi Chris,
Pad was switched to absolute device. See the 12-15-10 commit Switch
the pad to forced absolute mode:
http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/xf86-input-wacom;a=commit;h=ce98b0a20862291892fc7a3110e4779cd69dd5ba
And the commits around it.
Favux
On Mon, Jan
Never mind. While it's on the same usb channel as touch it would be a
different event, wouldn't it.
On Mon, Jan 10, 2011 at 10:16 AM, Favux ... favux...@gmail.com wrote:
Hi Chris,
Pad was switched to absolute device. See the 12-15-10 commit Switch
the pad to forced absolute mode:
Hi,
I would like to contribute two patches against the current git master.
Both patches are related to scroll/zoom gestures and were tested on a
serial Wacom tablet in Lenovo X201t.
The first patch is described in the following tracker issue: http://goo.gl/pyhax
A patch fixing the delay
No change in behavior using the wacom.ko from linuxwacom 0.8.8-10.
Same commit still breaks touch.
Favux
--
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be
I only have remote access to tablet right now but I noticed this in
the log file:
Wacom Bamboo 2FG 4x5 Finger touch: Wacom USB Bamboo tablet maxX=0
maxY=0 maxZ=256 resX=10 resY=10 tilt=disabled
I'm guessing the main issue is related to those zero values.
I'll have to study this new
Happened to boot to Win7 again, and must notice it is wholly different
experience there. Any luck with our driver?
On Sat, Jan 8, 2011 at 00:08, AndrewP inson...@gmail.com wrote:
I've compiled the driver from git, and now maxZ disappeared from Xorg.0.log
(http://dpaste.org/kwBe/)
everything
Hi Chris,
I think you're on to something. Here's what my logs are saying.
Both touch and pad are on:
[21.120] (**) Option Device /dev/input/event6
Xorg.0.log
[21.180] (--) Wacom BambooFun 2FG 4x5 Finger touch: Wacom USB
Bamboo tablet maxX=480 maxY=320 resX=25 resY=25
[21.230]
On Mon, Jan 10, 2011 at 10:52 AM, AndrewP inson...@gmail.com wrote:
Happened to boot to Win7 again, and must notice it is wholly different
experience there.
I know. They meant to be different since we counted on you, the users,
as well on Linux ;).
Any luck with our driver?
Not yet. No time
On Mon, Jan 10, 2011 at 3:10 AM, Cedric Sodhi man...@gmx.net wrote:
On Mon, Jan 10, 2011 at 09:16:14AM +1000, Peter Hutterer wrote:
On Sat, Jan 08, 2011 at 11:51:41AM +0100, Cedric Sodhi wrote:
I'm curious whether it would be possible and make sense to implement the
mode in which the pen
On Sun, Jan 9, 2011 at 6:33 PM, Peter Hutterer peter.hutte...@who-t.net wrote:
On Fri, Jan 07, 2011 at 11:10:30AM +1000, Peter Hutterer wrote:
On Thu, Jan 06, 2011 at 04:46:46PM -0800, Ping Cheng wrote:
On Thu, Jan 6, 2011 at 2:56 PM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Sun, Jan 9, 2011 at 5:26 PM, Peter Hutterer peter.hutte...@who-t.net wrote:
It's the device type name. The device name (identifier) is whatever the user
assigned in the configuration files. Same goes for other device types.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
Acked-by:
On Sun, Jan 9, 2011 at 5:28 PM, Peter Hutterer peter.hutte...@who-t.net wrote:
We're using them as type field, clients expect them, so let's export them
somewhere more visible.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
Acked-by: Ping Cheng pingli...@gmail.com
---
This patch
On Mon, Jan 10, 2011 at 03:03:55PM -0800, Ping Cheng wrote:
On Sun, Jan 9, 2011 at 5:28 PM, Peter Hutterer peter.hutte...@who-t.net
wrote:
We're using them as type field, clients expect them, so let's export them
somewhere more visible.
Signed-off-by: Peter Hutterer
On Mon, Jan 10, 2011 at 11:59:40AM +0100, Cedric Sodhi wrote:
thank you for this information, I'm looking forward to trying this out.
However, this does not adress my actual issue, which is, in an abstract
formulation
That I want to program the behaviour and the function of the keys.
But
On Mon, Jan 10, 2011 at 12:10:11PM +0100, Cedric Sodhi wrote:
On Mon, Jan 10, 2011 at 09:16:14AM +1000, Peter Hutterer wrote:
On Sat, Jan 08, 2011 at 11:51:41AM +0100, Cedric Sodhi wrote:
I'm curious whether it would be possible and make sense to implement the
mode in which the pen could
Here is what my bisect turns up:
At this commit, the cursor becomes overly accelerated or jumpy:
1e4d3d7060a1c438ac619cb64febb44bc45b47ed
Remove wcmInitialCoordiantes, move into wcmInitAxes
At this commit, it always slams into left wall:
6f5f29b49a6ebda7ae13ca9c32e6e16cf3181fc2
Purge screen
Much nicer to read, especially when viewed in patch context only.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/wcmValidateDevice.c | 37 +
1 files changed, 21 insertions(+), 16 deletions(-)
diff --git a/src/wcmValidateDevice.c
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/wcmCommon.c |8
src/wcmValidateDevice.c |2 +-
src/xf86WacomDefs.h |2 ++
3 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/src/wcmCommon.c b/src/wcmCommon.c
index 516d57c..352ec9e 100644
Overwriting the default option with the same value doesn't seem to be
useful. Also add a fixme, this code shouldn't be here in the first place.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/wcmValidateDevice.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
man/wacom.man |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/man/wacom.man b/man/wacom.man
index 79e799a..38852c8 100644
--- a/man/wacom.man
+++ b/man/wacom.man
@@ -120,7 +120,7 @@ to the X server, use 0 or
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
man/wacom.man |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/man/wacom.man b/man/wacom.man
index 38852c8..40a9673 100644
--- a/man/wacom.man
+++ b/man/wacom.man
@@ -118,9 +118,12 @@ To ignore the button
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/xf86WacomDefs.h |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/src/xf86WacomDefs.h b/src/xf86WacomDefs.h
index 3a680d1..c682ed6 100644
--- a/src/xf86WacomDefs.h
+++ b/src/xf86WacomDefs.h
@@ -178,7 +178,6 @@
At least one ! too many. Just remove the check, overwriting a value with the
already existing value in a non-time-critical path is not the end of the
world.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/wcmXCommand.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/xf86WacomDefs.h |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/src/xf86WacomDefs.h b/src/xf86WacomDefs.h
index c682ed6..6db7cda 100644
--- a/src/xf86WacomDefs.h
+++ b/src/xf86WacomDefs.h
@@ -177,7 +177,6 @@
OK, probably last email of the night. I notice this in xinput output
in patch were its good.
Label: Abs X
Range: 0.00 - 15360.00
Resolution: 0 units/m
Mode: relative
And it changes to this in the first patch were it
One last item for the night. The reason touch cursor totally stops
moving is related to removing code that set maxWidth/maxHeight but its
still referenced for relative devices (the commit mentioned below
removed it). Following patch gets back to jumpy cursor but is
obviously wrong:
diff --git
33 matches
Mail list logo
