Re: [Linuxwacom-devel] ScreenNo

2016-09-28 Thread Peter Hutterer
On Mon, Sep 26, 2016 at 01:52:54PM +0100, Markus Kuhn wrote: > On 21/09/16 12:05, Peter Hutterer wrote: > > these days a protocol screen like you use it is the exception, not the rule. > > > > the problem with ScreenNo isn't the ambiguity, it's that it just doesn't > > really apply when a screen i

Re: [Linuxwacom-devel] ScreenNo

2016-09-26 Thread Markus Kuhn
On 21/09/16 12:05, Peter Hutterer wrote: > these days a protocol screen like you use it is the exception, not the rule. > > the problem with ScreenNo isn't the ambiguity, it's that it just doesn't > really apply when a screen isn't already plugged in on boot. in many cases, > the screen order isn't

Re: [Linuxwacom-devel] ScreenNo

2016-09-21 Thread Peter Hutterer
On Fri, Sep 16, 2016 at 03:38:02PM +0100, Markus Kuhn wrote: > I am trying to use my Wacom Cintiq 13HD in what some call a > "ZaphodHead" configuration, i.e. where my xorg.conf file > has dual sections for Device, Screen and Monitor, > one for my regular 1600x1200 desktop display (DISPLAY=:0) and o

Re: [Linuxwacom-devel] ScreenNo

2016-09-17 Thread Juan
Hi Markus! I have a similar problem and I fixed this way: 1. Get your device name xsetwacom --list devices Wacom ... Pen stylus id: 11type: STYLUS 2. Your screen: xrandr -q Screen 0: minimum 320 x 200, current 4400 x 6000 (< I think that Wacom uses the sum of all real screens) HDMI9

[Linuxwacom-devel] ScreenNo

2016-09-16 Thread Markus Kuhn
I am trying to use my Wacom Cintiq 13HD in what some call a "ZaphodHead" configuration, i.e. where my xorg.conf file has dual sections for Device, Screen and Monitor, one for my regular 1600x1200 desktop display (DISPLAY=:0) and one for the 1920x1080 display in the tablet (DISPLAY=:0.1). Unfortuna