Thread: Kute File Monitor: A smarter file-trigger based launcher
View Single Post
Old 05-18-2016, 10:34 PM   #7
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by NiLuJe View Post
@Lucas Malor: At the very least in terms of thumbnails processing, yes. And since Nickel has to actually open the source file to process the thumbnail, that's a hit for fmon/kfmon.

Note that this is the behavior I noted on current FW versions (i.e., it does that on demand: library thumbnails are generated for the current page you're browsing in the Library, and the "last book opened" tile is generated when it has to be shown, the first time you close a new book). Nickel might have been doing some more aggressive stuff before, which might have triggered more bizarre behavior.
Or not. (After all, a number of people have been using fmon without encountering significant issues).
A very long time ago, the firmware generated all four cover images when the book was first added to the device. And it also generated and saved cover images for books on the external SD card. For sideloaded books, this was done during the book processing phase after disconnecting from the PC. Then, still a long time ago, but not quite so long, Kobo changed to generate the cover images as needed. And not to save the cover images for books on the external SD card (thought there is at least one firmware version that did). And changed where the cover images were stored. This has been the case for at least two years.

I am pretty sure that fmon was originally written during the first phase. That would have meant that fmon, or whatever called it, was not active at the point that the books were opened to generate the cover images.

Note: When reading this post, make the browser window very narrow, tilt the screen away from you and scroll the text just a little to fast to read easily. If your brain doesn't supply the correct theme music, hand in your nerd card.
davidfor is offline   Reply With Quote