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

Commit 0c4b89a6 authored by Winson Chung's avatar Winson Chung
Browse files

Remove usage of raw event coordinates for touch slop calculation

- This change was added in ag/3737691 for 2 button mode which is now
  removed from the system, using the raw coordinates is problematic
  since they depend on device orientation

Bug: 231636998
Test: Enable 3 button, rotate to landscape and verify unpinning works
Change-Id: I3f942a00570d516a7642182ff1412b17cd5464ff
parent 827c5557
Loading
Loading
Loading
Loading
+4 −5
Original line number Diff line number Diff line
@@ -273,9 +273,8 @@ public class KeyButtonView extends ImageView implements ButtonInterface {
                mLongClicked = false;
                setPressed(true);

                // Use raw X and Y to detect gestures in case a parent changes the x and y values
                mTouchDownX = (int) ev.getRawX();
                mTouchDownY = (int) ev.getRawY();
                mTouchDownX = (int) ev.getX();
                mTouchDownY = (int) ev.getY();
                if (mCode != KEYCODE_UNKNOWN) {
                    sendEvent(KeyEvent.ACTION_DOWN, 0, mDownTime);
                } else {
@@ -289,8 +288,8 @@ public class KeyButtonView extends ImageView implements ButtonInterface {
                postDelayed(mCheckLongPress, ViewConfiguration.getLongPressTimeout());
                break;
            case MotionEvent.ACTION_MOVE:
                x = (int)ev.getRawX();
                y = (int)ev.getRawY();
                x = (int) ev.getX();
                y = (int) ev.getY();

                float slop = QuickStepContract.getQuickStepTouchSlopPx(getContext());
                if (Math.abs(x - mTouchDownX) > slop || Math.abs(y - mTouchDownY) > slop) {