-
-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spams buttons when swapping to a Keyboard mode on a Pico #21
Comments
This is known, it is caused by the keyboard mode being rapidly constructed/destructed many times very quickly |
Would something like this fix the issue? I wrote this for Smash Box rocker toggles but it also ensures that you can't switch to the current mode. HayBox/config/mode_selection.hpp Lines 70 to 98 in 3459f03
|
Yeah, it makes it significantly more complicated for the average user to edit the mode bindings though, which I'd prefer to avoid. I feel like the real problem is just the way keyboard modes themselves exist in the current architecture. It doesn't really fit in well. Especially considering they don't even work with XInputBackend which is the default on Pico now, so you need to hold a button on plugin as well. Gonna have to redesign it at some point. |
Track index of current game mode config to prevent switching from one GameModeConfig to the same GameModeConfig, which in turn prevents spamming of keypresses when entering a keyboard mode on RP2040. Closes #21
When inputting the button combination for a Keyboard mode on a Pico, the device will rapidly spam those same 3 keys for maybe a second. For example, when inputing the Default Keyboard mode, it will spit out A, F, and H repeatedly in a long sequence. The sequence is variable, and appears to be related to how long all 3 buttons where held down after the button combination was inputed.
The text was updated successfully, but these errors were encountered: