Bug#483494: [Linuxwacom-devel] Bug#483494: xserver-xorg-input-wacom: problems with multiple screens

2008-06-03 Thread Magnus Vigerlöf
On torsdag 29 maj 2008, Ron wrote:
> Hi Jakob,
>
> I'm forwarding this to the linuxwacom list for confirmation and
> discussion, but I suspect this may be related to trouble with
> xorg 1.4 and the rescaling ...
>
> Magnus, is this just a misconfiguration issue, or a real problem?

I think the problem is connected with the rescaling issue of xserver 1.4, as 
you also suspect.
I think I've seen a bug report that the lw-driver doesn't honor the way the 
screens are laid out, but that would only explain why the pointer only moves 
on the left of the left and the right of the right, and not in the middle or 
on only one screen.

> If the latter, is there a known workaround, or is this something
> we are waiting on xorg 1.5 and the scaling code to be restored
> before it can be fixed?

Sorry, I don't know of a workaround.. What I would like would be to get the 
new Input API for the xserver defined and rewrite the driver from scratch 
(but other parts of my life keeps me a tad busy atm).

The rescaling code is in both 1.5 and master (which now has MPX merged), so 
this could be a good starting point. However in 1.4 and 1.5 there are a few 
things that has changed and it is fully possible that changes that affect the 
behaviour of our driver are not aligned with all Xorg versions.

Cheers
  Magnus

> Cheers,
> Ron
>
> On Wed, May 28, 2008 at 07:03:38PM -0700, Jakob wrote:
> > Package: xserver-xorg-input-wacom
> > Version: 0.8.0.2-2
> > Severity: important
> >
> > In my dual-headed setup, I run a single X session with two screens.
> > When using a wacom tablet as a pointer, anything left of center on the
> > tablet corresponds to the left half of my left monitor, and anything on
> > the right half of the tablet points to the right half of the right
> > monitor.
> >
> > So, if you were to number the halves of my monitors 1-4, left-to-right,
> > I can only actually access halves 1 and 4, and not touch 2 or 3 (the
> > insides).
> >
> > +-+-+  +-+-+
> >
> > |  1  |  2  |  |  3  |  4  |
> >
> > +-+-+  +-+-+
> >
> > -- System Information:
> > Debian Release: lenny/sid
> >   APT prefers unstable
> >   APT policy: (500, 'unstable')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/bash
> >
> > Versions of packages xserver-xorg-input-wacom depends on:
> > ii  xserver-xorg-core  2:1.4.1~git20080517-1 Xorg X server - core server
> >
> > xserver-xorg-input-wacom recommends no packages.
> >
> > -- no debconf information
>
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> Linuxwacom-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel




signature.asc
Description: This is a digitally signed message part.


Bug#483494: xserver-xorg-input-wacom: problems with multiple screens

2008-05-28 Thread Ron

Hi Jakob,

I'm forwarding this to the linuxwacom list for confirmation and
discussion, but I suspect this may be related to trouble with
xorg 1.4 and the rescaling ...

Magnus, is this just a misconfiguration issue, or a real problem?
If the latter, is there a known workaround, or is this something
we are waiting on xorg 1.5 and the scaling code to be restored
before it can be fixed?

Cheers,
Ron


On Wed, May 28, 2008 at 07:03:38PM -0700, Jakob wrote:
> Package: xserver-xorg-input-wacom
> Version: 0.8.0.2-2
> Severity: important
> 
> In my dual-headed setup, I run a single X session with two screens.
> When using a wacom tablet as a pointer, anything left of center on the
> tablet corresponds to the left half of my left monitor, and anything on the
> right half of the tablet points to the right half of the right monitor.
> 
> So, if you were to number the halves of my monitors 1-4, left-to-right,
> I can only actually access halves 1 and 4, and not touch 2 or 3 (the
> insides).
> 
> +-+-+  +-+-+
> | | |  | | |
> |  1  |  2  |  |  3  |  4  |
> | | |  | | |
> +-+-+  +-+-+
> 
> -- System Information:
> Debian Release: lenny/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages xserver-xorg-input-wacom depends on:
> ii  xserver-xorg-core  2:1.4.1~git20080517-1 Xorg X server - core server
> 
> xserver-xorg-input-wacom recommends no packages.
> 
> -- no debconf information
> 
> 
> 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#483494: xserver-xorg-input-wacom: problems with multiple screens

2008-05-28 Thread Jakob
Package: xserver-xorg-input-wacom
Version: 0.8.0.2-2
Severity: important

In my dual-headed setup, I run a single X session with two screens.
When using a wacom tablet as a pointer, anything left of center on the
tablet corresponds to the left half of my left monitor, and anything on the
right half of the tablet points to the right half of the right monitor.

So, if you were to number the halves of my monitors 1-4, left-to-right,
I can only actually access halves 1 and 4, and not touch 2 or 3 (the
insides).

+-+-+  +-+-+
| | |  | | |
|  1  |  2  |  |  3  |  4  |
| | |  | | |
+-+-+  +-+-+

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xserver-xorg-input-wacom depends on:
ii  xserver-xorg-core  2:1.4.1~git20080517-1 Xorg X server - core server

xserver-xorg-input-wacom recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]