Quote:
Originally Posted by Sirtel
No, it's not that. When they don't respond, they don't respond until you touch the screen, no matter how many times or how hard you press the button.
|
FWIW, I *cannot* reproduce that in KOReader.
Whether it be the Elipsa's panel or the Sage's buttons, I can only ever miss *a single* gesture, and only if that event is a wakeup source (that's generally a single press down -> up for buttons, and a single contact down -> up for the panel, although it's more complicated there because it also suffers from spurious 0-pressure events issues). Duplicating the offending gesture works immediately (and the kernel is woken up by the missed input).
(For those missed inputs, I've also *never* seen weirder crap like only seeing an up without a down, or vice-versa; or even parts of it being interleaved with a later input frame; something which could arguably confuse the hell out of a finger tracking algo. AFAICT, the entire gesture gets sent into the void and never hits userland.).
I've never seen the "stuck" issue either on my device, but KOReader's KEY_REPEAT handling is fairly basic, so there may be a bit of software tomfoolery there, even if I've never actually seen spurious REPEAT events myself during my extended time poring over input frames on those devices
.