TouchInputMapper: Use ui::Transform to calculate orientation angles
Rather than manually re-orienting the calculated angles for orientation
and tilt, we use the transform to compute the oriented values for these
non-planar axes. This approach is both less error-prone and less verbose.
In this CL, we also transform the coverage rect from raw to display
space using the computed transform.
Bug: 236798672
Test: atest inputflinger_tests
Change-Id: Ibfb6d2ab43e6fd7a63736ee7d9610c42be44affd
diff --git a/services/inputflinger/reader/mapper/TouchInputMapper.h b/services/inputflinger/reader/mapper/TouchInputMapper.h
index 1a583c0..29b850f 100644
--- a/services/inputflinger/reader/mapper/TouchInputMapper.h
+++ b/services/inputflinger/reader/mapper/TouchInputMapper.h
@@ -428,12 +428,8 @@
// the rotated coordinate space. See mPhysicalFrameInRotatedDisplay.
ui::Transform mRawToRotatedDisplay;
- // Translation and scaling factors, orientation-independent.
- float mXScale;
- float mXPrecision;
-
- float mYScale;
- float mYPrecision;
+ // The transform used for non-planar raw axes, such as orientation and tilt.
+ ui::Transform mRawRotation;
float mGeometricScale;