Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properly calibrate the input device #59

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

blaztinn
Copy link

Current calibration didn't properly calibrate the input device if the display screen was rotated or if one of the axis was mirrored by the HW. Maybe it didn't work in other cases too, but this are the ones I know of.
This patch fixes this problems by properly calibrating the input device on any possible click sequence, previous calibration and axis inversion (min-max switched).

First commit updates tester to test for all the possible sequences (before there was a missing click sequence where the y coordinate is changed first!)

The second commit updates the generic and evdev calibrations to properly calibrate the screen and pass the tests.

I've successfully tested this changes on two touchscreens (IR and SAW) which have different axis ranges and inversions.

Update tester to test different possible sequences of clicks

Signed-off-by: Blaž Tomažič <blaz.tomazic@gmail.com>
Update generic and evdev calibrators to calibrate the input depending on
the sequence of the clicks and independent of the orientation of the
screen.

Signed-off-by: Blaž Tomažič <blaz.tomazic@gmail.com>
@blaztinn blaztinn changed the title Properly calibrate the input Properly calibrate the input device Mar 19, 2014
@austriancoder
Copy link
Contributor

Tested-by: Christian Gmeiner christian.gmeiner@gmail.com

@La0
Copy link

La0 commented Aug 22, 2014

We use with success this pull request in our own debian package @ivsgroup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants