View Single Post
Old 05-24-2020, 11:52 AM   #11
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@OfficerAction: Yeah, I saw that a rotation could be fed, I just hadn't seen a frontend bit to confirm what you were feeding it, exactly .

(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?).

Last edited by NiLuJe; 05-24-2020 at 12:26 PM.
NiLuJe is offline   Reply With Quote