View Single Post
Old 02-08-2016, 04:15 PM   #1804
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
@Andrewzz: You're most likely reading a KFX book. Try with the latest snapshots.
Or your current read simply has no proper cover set in its metadata (... or it's a PDF. Or a periodical?).

@qqqqqqqqqqqz:

1. shuffle is basically a no-op on FW 5.x (unless you enable the usb watchdog, which is most likely useless, hence it being disabled by default).

Both settings do the same thing, they just potentially do it at different times (hack startup for random, watchdog restart for shuffle. The "restart framework" button in KUAL will trigger a hack startup, hence the deprecation of the watchdog).

2. While completely doable in theory, it sounds way messy to handle on the user's side, and I personally have no interest in implementing this. In the same vein as my next answer, that's on the user's hands. Nothing is preventing you from spiking your pool with duplicates to game the sorting process .

3. Slightly annoying to implement for performance reasons (it would imply keeping a copy of the pristine images somewhere, and re-processing them at each startup. The composition process is *extremely* expensive, so it's kind of a no-no, you'd basically sit around waiting for the framework to start for no good reason).


We're already processing stuff in cover mode, and only doing it image per image, once the framework is up, so we can sweep the performance aspect under the rug without too much trouble.


Plus, those images are already user-provided, so, if some extra info is needed, that's entirely in the user's hands. (It's the same reasoning behind the lack of a "magically dither all my custom screensavers" button in KUAL: I leave that to the user).

It's trivial to batch-process with ImageMagick, and is much faster on a desktop anyway.

Last edited by NiLuJe; 02-08-2016 at 04:20 PM.
NiLuJe is offline   Reply With Quote