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 one for
> the 1920x1080 display in the tablet (DISPLAY=:0.1).
> Unfortunately, I have not managed to find a way in xorg.conf
> to constrain the stylus range of the Wacom tablet to just one
> of my two Screens (namely the DISPLAY=:0.1 one). Instead, the
> stylus always travels horizontally across a 1600+1920 wide
> virtual screen, which obviously breaks positioning on the tablet
> I just noticed that the exact functionality I was hoping for did
> in fact exist in the past, in form of
> Option "ScreenNo" "1"
> but was removed in commit 4ffd3c64ca29a637bf1d2c69b11e360e8d8a82f5:
> Author: Peter Hutterer <peter.hutte...@who-t.net> 2010-11-24 05:02:15
> Purge ScreenNo handling.
> The definition of ScreenNo isn't clear, given that we have RandR
> ScreenRecs and protocol screens, not all of which overlap totally. Let
> mapping of the tablet to a given area on the available desktop be
> handled by
> a client.
> That removed option seemed to do exactly what I wanted (for
> protocol screens) ... :-(
> Is there now any other way in /etc/X11/xorg.conf.d/ (or a similar
> global config file) to bind the absolute coordinate range of a wacom
> tablet to just one single screen?
> I would very much like this binding between screen and tablet
> to be done properly from the very beginning by the X server,
> in a system-wide configuration file for all users (like xorg.conf),
> before the user logs into a display manager. I therefore would
> like to avoid user clients such as "xsetwacom set 14 MapToOutput ..."
> that only kick in after login.
> Is there no chance to bring Option "ScreenNo" back,
> perhaps with a slightly changed syntax to make the
> semantics unambiguous?
> What was gained be dropping the existing multi-head support
> from the driver?
maintainability. ScreenNo predates the ability to hotplug screens in X,
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 clear until after login, e.g. when you use xrandr to
arrange the displays.
Linuxwacom-devel mailing list