Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 1f1a42b5 authored by Linzhao Ye's avatar Linzhao Ye Committed by Automerger Merge Worker
Browse files

Merge changes from topic "ToupadPointerCapture" am: be23210b am: 888e5ea1 

Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/1447900

Change-Id: I9c0b1578364c981f76a5f1bf67d06969cc9d4d79
parents 96fb6c70 888e5ea1

services/inputflinger/reader/mapper/TouchInputMapper.cpp

+5 −4
Original line number Diff line number Diff line
@@ -191,10 +191,11 @@ void TouchInputMapper::populateDeviceInfo(InputDeviceInfo* info) { 
        info->addMotionRange(mOrientedRanges.pressure);



        if (mDeviceMode == DeviceMode::UNSCALED && mSource == AINPUT_SOURCE_TOUCHPAD) {

            // Populate RELATIVE_X and RELATIVE_Y motion range for touchpad capture mode

            // RELATIVE_X and RELATIVE_Y motion range is the largest possible hardware relative

            // motion, e.g. the hardware size finger moved completely across the touchpad in one

            // sample cycle.

            // Populate RELATIVE_X and RELATIVE_Y motion ranges for touchpad capture mode.

            //

            // RELATIVE_X and RELATIVE_Y motion ranges should be the largest possible relative

            // motion, i.e. the hardware dimensions, as the finger could move completely across the

            // touchpad in one sample cycle.

            const InputDeviceInfo::MotionRange& x = mOrientedRanges.x;

            const InputDeviceInfo::MotionRange& y = mOrientedRanges.y;

            info->addMotionRange(AMOTION_EVENT_AXIS_RELATIVE_X, mSource, -x.max, x.max, x.flat,