You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
-
That's true... So yes, this could cause an issue. I guess the cheap
fix would be to suspend transferring of other button presses until
25ms after the button is pressed?That would work too. So the moment it receives 'rising' or 'state=true' to that handler, it must not propagate ( should consume/return from function ) all future signals until 25 ms has past. Including future falling signals and including future rising signals.
That's true... So yes, this could cause an issue. I guess the cheap fix would be to suspend transferring of other button presses until 25ms after the button is pressed?