Quote:
Originally Posted by davidfor
OK, I have had a look at the database and the cover file name sent. The database has record of 133 books. These break down to:
- 6 sideloaded books
- 99 books are purchased from Kobo but are not on the device. Just the details are in the database. Five of these were downloaded on 02/06/2015 and then removed.
- 28 are recommendations that were downloaded 02/06/2015.
There will be at least one cover image file on the device for each of these books. There should be somewhere between 133 and 432 cover image files. The .kobo-images directory has some other images for thing like the awards.
Based on what you have said, I assume 02/06/2015 is the date you set this device up. |
I think so, I really don't know when purchased the glo HD, it was at release date.
Quote:
|
Because of the way this is done, the directory can have cover images for more than one book. And as they will be reused, there is no real reason to remove them. The utilities plugin does remove them, but that was my decision when I wrote the code.
|
So I have to remove them manually ?? it is just that I don't like stuff on the internal card that doesn't "belong" there.
Because I don't re-sync the images would be there all time ?? it now takes the space of about 54 ebooks..
I am not a "utility writer" but I would love a utility that would scan the book directory's and remove images of covers that are not on the reader.
When I manually remove them, would the database will be upgraded ??
Thank you for your work, I think the best way is to "now and then" run the directory's and clean what is no longer there, but I see also a problem with that.. now the dates are simple to find back, all the same of the second of june.. but in later progress dates will be more different and more close to the real date.
I just don't like it that space is been occupied with something there is not longer there.
Also I don't see any possibility to stop sending reccomendations.. I just synced to see if that would remove some not used bookcovers and update the database,but in stead of that, 48 new recommendations are sended..
I am still looking to a way to force rebuilding of the database,does it grows more and more when entry's stay in it for books that are no longer there ??