Closed as not planned
Description
Feature Request Type
- Core functionality
- Add-on hardware support (eg. audio, RGB, OLED screen, etc.)
- Alteration (enhancement/optimization) of existing feature(s)
- New behavior
Description
In the docs I see that RETRO_SHIFT
can be configured with a timeout.
If
RETRO_SHIFT
is defined to a value, hold times greater than that value will not produce a tap on release. This enables modifiers to be held for combining with mouse clicks without generating taps on release. For example:#define RETRO_SHIFT 500
I think adding the same behaviour to RETRO_TAPPING
would be a great with exactly the same reasoning as stands for RETRO_SHIFT
. What do you think about that?