You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
The tap should begin immediately upon trigger, as it does when "Hold down" option is not used. If "Hold down" is used the trigger button is pressed and released in a short amount of time, atleast 1 tap event should occur.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Device: Pixel 2
Android version: Android 11
Additional context
I'm developing a Morse code related app that I have tuned to 300ms. That's where I got the 300ms duration from. I was able to produce the problem in other apps too, so I know it's not just my app.
I was able to workaround this by making 2 keymaps:
One with a tap coordinates action without the hold down option
One with a swipe coordinates action that has a 350ms swipe duration. The 350ms is hard coded though
The text was updated successfully, but these errors were encountered:
Developer TODO (don't remove)
Discord message link/email recipient
Describe the bug
Two closely related bugs when using the Tap Coordinates action with a "Hold down until trigger is released" option:
To Reproduce
Steps to reproduce the behavior:
Upload a backup of your keymaps. Follow the guide here
tap_hold_down_bug_key_maps_20250122-124628.zip
Expected behavior
The tap should begin immediately upon trigger, as it does when "Hold down" option is not used. If "Hold down" is used the trigger button is pressed and released in a short amount of time, atleast 1 tap event should occur.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Additional context
I'm developing a Morse code related app that I have tuned to 300ms. That's where I got the 300ms duration from. I was able to produce the problem in other apps too, so I know it's not just my app.
I was able to workaround this by making 2 keymaps:
The text was updated successfully, but these errors were encountered: