View Single Post
Old 05-25-2020, 12:40 PM   #12
OfficerAction
Connoisseur
OfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughingOfficerAction can shake the floor when laughing
 
Posts: 80
Karma: 63118
Join Date: May 2018
Device: Kobo Aura One
Quote:
Originally Posted by NiLuJe View Post
(I'm *hoping* Qt can actually deal with the various protocol quirks sanely on its own (at least for basic touch events, multi touch gestures might be a tougher ask), but I wouldn't necessarily bet my life on it ^^. IIRC, the Aura One is using roughly Multi Touch B w/o ABS_MT_SLOT and w/ possibly broken timestamps (since boot instead of epoch, AFAIR)).

Which leads to my next question: do you deal with rotation in your app, and if so, how? (hardware fb rotations, or a rotated sw viewport?).
I have not tried multitouch. In theory it should have support for all of that but unfortunatly in practice there are issues. Even for swipe gestures I had to reimplement some parts. Don't pin me down on that but I think the problem was that the touch inputs got mapped to mouseclick events and the builtin guesture recognizer didn't like that.

For the rotation I just use FB rotation at startup. SW rotation in Qt is also possible but it just seems cleaner that way.
Actually for that and the whole Nickel exit and restart sequece I used parts of the Koreader scripts, they helped out a lot
OfficerAction is offline   Reply With Quote