@r00t
AL’s approach to input-handling polls for async device state (asking “which buttons and keys are down, right now”) , on a 30ms timer – and looks for differences between “now state” vs previous timer tick.
Then, yes there’s also a ~1 second clock which is meant to drive the “flashing” UI text… which may be responsible for the superficial part of this bug.
I do plan to improve and simplify all this timer-logic, but it’s a pretty fundamental change – not a quick bugfix.
For now, I say simply avoid doing that? viz. don’t define separate ‘press’ and ‘release’ behaviors on buttons that are part of a mutually-exclusive grouping – it’s meant for cases where there’s not going to be roughly simultaneous button2down+button1up events.
(But thanks for the continued deep-dive bug reporting.)