ram that creates a virtual uinput touch
device and transforms touch positions according to its own transformation
configuration.
I really appreciate your help. Without your help, I couldn't solve this
problem.
Best regards,
Hugh Chang
___
se?
I'll appreciate any clue and I'm willing to try as much as I can.
My current installation is the clean ubuntu-18.04.5-desktop-amd64.iso.
> GNOME's mutter has an automatic touch screen mapping using heuristics.
This
> may be the reason it fails on 18.04 if the heuristics get
Thank you very much for this great information.
I'll investigate the source code of GNOME's mutter to find why
EETI (eGalaxTouch) works well and the other does not on Ubuntu
20.04 (not 18.04).
Best regards,
Hugh Chang
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
ix value is set correctly and touch works well even if
I did not specify it on Ubuntu 20.04. For other touch monitors, I need to
specify it manually in a configuration file.
Would you let me know where to start my investigation please?
--
Hugh Chang
__
erLayout"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" 0 0
EndSection
When all the origins are (0,0), however, I don't know what to do
as I described in "4.2.2. ServerLayout without position information" of
"https://lists.x.org/archives/xorg/attachments/20200717/37b0cae6/attachment-0001.pdf";,
Best regards,
Hugh Chang
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
origins.
However, my customer is saying that they are independent screens and do
not overlap even when the origins are all (0,0).
How can I transform the input touch positions properly in this environment?
Best regards,
Hugh Chang
--
