On Mon, Mar 26, 2012 at 05:34:12PM +0000, Ammo Goettsch wrote: > [re-transmitted as ASCII mail] > > In this bug: https://bugzilla.gnome.org/show_bug.cgi?id=602733 > > I am taking the position that remapping for Xinerama isn't the job of > an input device driver, but that GDK should take care of it. Note the > patch I submitted allows you to specify "Current Monitor" as the > coordinate space binding, so that Cintiq and similar devices will work > correctly in multi-screen environments. > > I know about the workaround of setting the coordinate mapping to the > entire virtual desktop, but I would say that is sub-optimal, because > it does not survive displays being added/removed and it does not allow > you switch active monitors. > > Would someone from this list like to comment? Do you plan to have > the driver solve this instead (and act like the mouse or core pointer > device?) Would you agree that this is out of bounds / level > violation to solve this in the driver?
yes, it's out of bounds for the driver. Note that GNOME 3.4 has this now fixed for XRandR 1.2 setups. Together with libwacom, a Cintiq will automatically map to the right monitor. http://www.hadess.net/2012/01/wacom-tablets-in-gnome-34.html http://www.hadess.net/2012/02/wacom-tablets-in-gnome-34-part-2.html NVIDIA is still an issue, but that's hopefully not too far off either. libXnvctrl is a bit of a pain from what I gathered. Cheers, Peter ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
