MobileRead Forums - View Single Post

FJames · 03-13-2012, 10:56 AM

The problem is not that the KT misses taps occasionally. That's going to happen with any touch screen, and it's not a big deal as long as it's not frequent - you just tap again. The problem is that often the KT will then double-page-turn on the next tap, meaning you have to recognize the double page turn and tap again a third time to go back a page. That's annoying, especially since it's a bug that should be easily preventable by proper firmware design. What's happening is that the KT is getting half the tap, i.e., it clearly recognizes that you have put your finger down, but not that you have lifted it up. It's obviously waiting for you to complete your gesture, and only when you tap again does it realize that you're not making a gesture (an alternate theory would be that it's actually busy for longer than usual processing the page turn for some reason, but that's ruled out by the fact that you can wait as long as you like and no page turn happens until you tap again). In that case it should single-page-turn, not double-page-turn. That would seem to me to be an easy change, but maybe there's some problem separating this error situation from legitimate gestures?

03-13-2012, 10:56 AM	#472
FJames Addict Posts: 320 Karma: 320941 Join Date: Jun 2011 Location: Canada Device: Kobo Touch & Aura	The problem is not that the KT misses taps occasionally. That's going to happen with any touch screen, and it's not a big deal as long as it's not frequent - you just tap again. The problem is that often the KT will then double-page-turn on the next tap, meaning you have to recognize the double page turn and tap again a third time to go back a page. That's annoying, especially since it's a bug that should be easily preventable by proper firmware design. What's happening is that the KT is getting half the tap, i.e., it clearly recognizes that you have put your finger down, but not that you have lifted it up. It's obviously waiting for you to complete your gesture, and only when you tap again does it realize that you're not making a gesture (an alternate theory would be that it's actually busy for longer than usual processing the page turn for some reason, but that's ruled out by the fact that you can wait as long as you like and no page turn happens until you tap again). In that case it should single-page-turn, not double-page-turn. That would seem to me to be an easy change, but maybe there's some problem separating this error situation from legitimate gestures? Last edited by FJames; 03-13-2012 at 11:00 AM.