TouchInputMapper: Perform physical frame hit test in rotated display space
The physical frame is specified in DisplayViewport in the rotated display space. The frame is not symmetric along the X or Y axes because the right and bottom edges are outside of the frame. For example, for a physical frame with bounds [left, top, right, bottom], any point with an x value of `right` or y value of `bottom` is outside the frame, whereas points in the frame could contain an x value of `left` and a y value of `top`. To address this asymmetry, we must perform any hit tests in the intended coordinate space, which in this case is that of the rotated display. This logic is tested again in following CLs. Bug: 236798672 Bug: 257118693 Test: atest inputflinger_tests Change-Id: I403a686c437aa53cb808910b296a7251e0e96321
Loading
Please register or sign in to comment