I tested the button code change and it doesn't seem to address the glitch I'm seeing.
I have figured out the usage scenario where it crops up and a usage workaround though.
- If a different button is pressed, it must be pressed slowly to not register as the same button press.
It is particularly noticed when changing settings. When pressing a
different button, a slow (~0.25s) press is required. If just "clicked" the click is registered as the
previous button pressed.
To reproduce:
- Press LEFT+RIGHT to enter settings.
- Slow click (~0.25s+) the RIGHT button.
- Next, a "quick-click" to either the MIDDLE or LEFT button changes to the next screen that should display by pressing the RIGHT button. This continues indefinitely unless the "click" is slowed to a "press".