View Single Post
Old 06-17-2021, 11:30 PM   #3
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
There are approximately a billion ways of achieving what you vaguely describe, so, more details would be nice.

In no particular order:

* If it's standard document types you're working with, KOReader has an auto-turn plugin.
* I'm pretty sure people have written multiple things related to sending synthetic button/touch events in the past, so, that's an option too in stock-land.
* If you do intend to work with stock screensaver, the ScreenSaver's hack cover mode is essentially generating a screensaver at runtime. The trick being, if there's only one file in the pool, it'll get picked up, so just update that one file over and over.
* Otherwise, DIY w/ FBInk in C/C++/Python/Lua/Go/(shell), in which case, sky's the limit.
NiLuJe is offline   Reply With Quote