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
{{ message }}
This repository has been archived by the owner on Apr 11, 2023. It is now read-only.
Debouncing is currently configured at the beginning of the main.cpp file with a fixed 5ms delay. At the very least this should be editable via the web configurator.
A more robust implementation would have preset values for certain types of devices. For instance stock Sanwa JLFs may need more than the stock 5ms debounce delay, but the normal buttons may not. Would be nice to say "set debounce to X for directionals/stick and Y for buttons".
The text was updated successfully, but these errors were encountered:
This should definitely be part of the button redo.
To me it seems like physical buttons.. pins… whatever correspond with something button wise, and there’s where LEDs and denounce belong.
For example, if someone made a controller that has both buttons and a stick for movement, debounce values might be different for the stick direction than the button direction
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Debouncing is currently configured at the beginning of the main.cpp file with a fixed 5ms delay. At the very least this should be editable via the web configurator.
A more robust implementation would have preset values for certain types of devices. For instance stock Sanwa JLFs may need more than the stock 5ms debounce delay, but the normal buttons may not. Would be nice to say "set debounce to X for directionals/stick and Y for buttons".
The text was updated successfully, but these errors were encountered: