It is still a problem, partially.It is possible to use coordinate
transformation matrix property (TransformationMatrix option in
InputClass section) to assign touchscreens to different displays, but
not to different X screens. But, unless system is SLI , or , or Mosaic
enabled - that is , it is
Public bug reported:
On system with several X screens on same server, e.g. several GPU cards that
doesn't support functions similar to TwinView or BaseMosaic of NVIDIA, evdev
doesn't map coordinates of touch events properly.
For example if on server :0 there are two displays connected to
https://launchpad.net/ubuntu/+source/xorg-server/2:1.13.0-0ubuntu6.1/+build/4015022
last build still too old, so seem it doesn't contain this? e.t.a. for update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Addition to bug info:
Without a fix, users cannot reliably use a rotated touchscreen.
Without fix users unable to use serveral screens one or more of which
are touchscreens, on systems or drivers which do not support separate
coordinate systems for each physical screen, e.g. ATI FireGL or
Looks I'm getting same eefect with newest releases of Ubuntu and evdev drivers
(tried alot of combos,throughout 2012 year).
Simply, using transformation matrix with evdev driver wich inverts, scales or
shift coordinates causes either jumping to border of screen or jitter when
touch
@Cris: probably because of it's not clear in which order they will be
applied if matrix also used.
Can you suggest link to distro which got it included, I need test it
aap, as I have important project hanging which incdues about hundred
devices with multiple screens and touchscreens. Was
