On multi-choice screens I often hit the wrong choice accidentally on the way to selecting the correct choice or sometimes hit the wrong choice and immediately touch the correct choice before the next screen is rendered.
In each case the second touch is accepted on the following screen not the intended screen so I end up with the wrong answer on two consecutive screens rather than one (which I accept is my error).
If there was a very short delay after rendering multi-choice screens where inputs are ignored ie the fastest response time (250ms?) it would alleviate these unintentional carry-over touches.
1 Like
Noticed the same. It should wipe any input buffer after the screen is fully displayed.
It’s a known issue in signaling, how to avoid recording one action as twice due small interruptions.