MobileRead Forums - View Single Post

NiLuJe · 12-08-2019, 01:12 AM

Bonus points if you fix KSM to actually use the proper current fb orientations on (at least) Mk. 7 devices, because that's currently not the case

.

(That part is accurate in FBInk, because KOReader relies on it, c.f., utils/fbdepth.c, with extensive comments about the exact behavior on the devices I own, scattered around set_kobo_quirks() in fbink_device_id.c and initialize_fbink() in fbink.c, with a bit of extra posssibly-not-entirely-accurate fun thrown in around rotate_touch_coordinates()).

If that's actually a viable approach with Sergey's Qt4 plugins, of course. Because they may assume and expect the broken behavior, but I wouldn't know about that

.

12-08-2019, 01:12 AM	#706
NiLuJe BLAM! 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	Bonus points if you fix KSM to actually use the proper current fb orientations on (at least) Mk. 7 devices, because that's currently not the case . (That part is accurate in FBInk, because KOReader relies on it, c.f., utils/fbdepth.c, with extensive comments about the exact behavior on the devices I own, scattered around set_kobo_quirks() in fbink_device_id.c and initialize_fbink() in fbink.c, with a bit of extra posssibly-not-entirely-accurate fun thrown in around rotate_touch_coordinates()). If that's actually a viable approach with Sergey's Qt4 plugins, of course. Because they may assume and expect the broken behavior, but I wouldn't know about that . Last edited by NiLuJe; 12-08-2019 at 01:20 AM.