libretro / libretro/RetroArch

[Android] Double touches move cursor to the edge of the screen

Open
#14,012 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

input: touch platform: android
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

The two-finger right click often moves the cursor to the far edge of the screen. Here's a video.

It seemed to do this regardless of finger distance. It is caused by a slightly imperfectly timed double touch

Expected behavior

Touches are registered as a double touch in the center of your two touches

Actual behavior

Cursor flies to the edge of the screen

Steps to reproduce the bug
  1. Open a game with DOSBox or Desume
  2. attempt to right click (DOSBox only) by double touching, but delay one finger's touch just a bit.
Bisect Results

Basically if the touches are rejected as a double touch, meaning not simultaneous enough but nearly so, it considers both touches as the trajectory of a single drag. So you can make this happen in any direction intentionally.

Version/Commit

RetroArch: AArch64

RetroArch Info

Screenshot_20220531-072728
Screenshot_20220531-072742
Screenshot_20220531-072748
#Screenshot_20220531-072754

Environment information
  • OS: Android 12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the delayed two-finger touch on Android, then trace the touch handling that distinguishes a double touch from a single drag; done means near-simultaneous touches register at their center instead of moving the cursor to the screen edge.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, c
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.