Quote:
Originally Posted by robko
I think it's some combination of user, firmware and possibly hardware. People that have the problem seem to always have it and in some cases across multiple devices or replacements. There really isn't a lot to a tap or swipe, so not sure how it could be user, but it seems a lot of the people with the problem, always have the problem. I'm in the "have had it before (quite a while ago), don't get it anymore" camp. It is an extremely annoying issue if you have it. There seem to be less people with the problem these days or they don't mention it anymore at least.
|
This reminds me of user that I had for a program I wrote several years ago. At one point in the program there was a button that could be clicked on to perform some action and this one particular user complained that it wasn't working properly. Try as I might I couldn't get it to fail for me, so I went around to her house to see her using the program. When it came time to click on the button she double clicked it instead of just a single click. I pointed this out to her but she insisted that she only single clicked it. So we did it again and again I saw her double click it, but again she swore that she only single clicked it! This was before mobile phones had video cameras built into them, so I couldn't film her doing it. My guess is that she was just so used to double clicking most other buttons that it was just second nature to her to double click ALL buttons. I modified the program to detect a double click and throw away the second click and she was happy.
The double page turns that some people are seeing also reminds me of
keyboard debouncing. When people press keys they do so for varying amounts of time, measured in split-seconds. My keypress might be ever so slightly longer or shorter than your keypress. Also the way I press a key might make it make contact with the underlying sensors several times per key press. To fix this problem engineers invented "keyboard debouncing". I assume that something similar is used for touch screens, maybe Kobo need to fine-tune their debounce algorithm a bit?