Quote:
Originally Posted by simonchik
@Markismus: thank you. Yes, that must be a protocol problem. Swiping gestures don't work at all.
So the touch events are the "39161 EV_SYN 0 0 " (# tev fed| 32 | 739161 | 209 | 114 | -1 | Evt 0) thingies, huh?
Maybe could we try in, say, input.lua or gesturedetector.lua to block those tevs? I see that in input.lua there is "if Device:getModel() ~= 'Kobo_phoenix", could this be used for the mark3 as well? Or maybe the function "function GestureDetector:feedEvent(tevs)" could be hacked?
|
You have two touch events associated with a tap. Screen touch and touch release. The -1 is a release, the 1 at the same location in other
tev fed is a touch.
If the touch release doesn't happen for a while, than the code interprets it as a hold. If you touch very slightly and touch again --trembling fingers or something like that-- it could be registered as a double tap.
A single tap gesture would turn the page, a hold gesture would select a word for highlighting or translation and a double tap would zoom the page (if enabled in
defaults.lua.)
Everything can be hacked. But I would suggest that you get telnet up and running, that you get the debug output to the telnet terminal instead of the log file, that you experiment with what kind of touches generate what kind of gestures.
When you have a clear idea what is happening, I would suggest hacking
gesturedetector.lua until you have something that works. Important are the constants in
GestureDetector (line 44-55). First try fiddling with these to see what the do and what impact they have on your gestures. Open an issue in github to address your problem and report your findings. The developers are really helpful.