View Single Post
Old 08-01-2014, 08:58 PM   #1250
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,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@ssholloway: Because switching between cover and other modes is done at the same early point in time during boot when the hack starts, so you can't really do it at runtime with how it's designed right now (which is also why each 'mixed' mode feature request went unimplemented) .

You can trigger that part of the code slightly faster than a full reboot w/ the 'Restart X' button of the Fonts hacks, which restarts the whole graphics stack (lab126_gui), and not simply the framework.

EDIT: And to answer the second part of your message, because in cover mode, the linkss/screensavers folder is unused, it's not even looked at, the active file is hosted outside of the userstore.

Which technically means, that, at best, for one your usecase, you could tweak the KOReader startup script to setup a single 'KOReader' screensaver, and switch back to the last cover on quit, but that's all.
Nothing much you can do about crappy covers, except fixing the files' metadata before putting them on the device .

Last edited by NiLuJe; 08-01-2014 at 09:04 PM.
NiLuJe is offline   Reply With Quote