Thread: Kute File Monitor: A smarter file-trigger based launcher
View Single Post
Old 07-11-2018, 10:58 PM   #89
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,905
Karma: 47303824
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
But deleting a single one yields weird results, IIRC (the placeholder thumbnail with a question mark, I think), and it doesn't get regenerated until the next Nickel boot, AFAICT.

Take that with a grain of salt, it's been a while since I checked. I can only confirm that a delete + reboot does the job 100% of the time .
Exactly what happens when you delete the cover image seems to depend on if the cover is in the cache. The reboot will trigger them to be regenerated the next time they are needed. But, I think if you remove the covers when they aren't in the cache, then the reboot is not needed. That's hard to test as the act of looking puts the cover in the cache and I don't know how big it is.

Or, it might not be a cache, but an open file handle or something that gets invalidated when the image file is removed, but not checked properly when they attempt to use it.

There is also a problem if you don't delete all the cover images for a book. If you only delete the largest on (used for the sleepcover) it isn't always regenerated. One of the smaller sizes gets used. The reboot doesn't fix this. I did some playing with this earlier in the year to see if some space by deleting the largest image after the others had been created. I was hoping it would generate the largest when the book was opened or device put to sleep, but it didn't. It actually used one of the smaller images and looked terrible.
davidfor is offline   Reply With Quote