[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-xorg
Subject:    Re: Confusing interactions between xinput mapping and xinput set-prop
From:       Peter Hutterer <peter.hutterer () who-t ! net>
Date:       2019-03-14 22:40:08
Message-ID: 20190314224008.GA29071 () jelly
[Download RAW message or body]

On Thu, Mar 14, 2019 at 10:59:06AM +0000, malcolm moore wrote:
> If I use xinput set-prop to change the calibration matrix ( because I am
> trying to use a SmartBoard as a second touch screen which are notoriously
> inaccurate ) I can set the values to whatever I like. So far so good, but
> then I have to do the xinput --map-to-output to tell the machine where the
> touch is coming from. This resets the values I first set. If I do the
> xinput --map-to-output first the xinput set-prop resets that. How do I do
> both

you can't. map-to-output is a convenience helper because it's the prime
use-case for the calibration matrix and in the end writing map-to-output
was more efficient than explaning how to set the calibration matrix to every
user that filed a bug report.

If your touchscreen needs calibration *and* screen mapping, you need to
manually calculate the matrix and then set it directly.

Cheers,
   Peter



_______________________________________________
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
[prev in list] [next in list] [prev in thread] [next in thread]