Thread: [GUI Plugin] Kobo Utilities
View Single Post
Old 06-17-2013, 06:41 AM   #99
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 jgoguen View Post
Would it work to say that you don't change the reading state on auto-updates? So if I have a purchased and side-loaded KePub with some percentage read, when I reset and reload these would be unread (except the purchased one may already have it's reading state set). Then the plugin would not update the side-loaded book because the reading state is different. Similarly, the purchased book would either be a different reading state or identical and not updated anyway.

Or I'm way out in left field
Firstly, I leave the purchased kepubs to Kobo. They can sync the reading position, so I let Kobo take care them.

For sideloaded books, my intention is have a way to automatically store the current reading position. It will probably be an extra job run after the current ones have finished.

At least on the first release, restore will stay manual. After a factory reset, sideload the books, let the device process them. Reconnect, select all the books that are on the device and restore the reading position. Preventing the automatic job from running or overriding the reading positions in calibre is the concern.

I think it actually works now, though I haven't tried it for a while. The "Clear if unread" is supposed to work like that. If this is not checked, and you store the position of a book that is unread, it should not change the calibre library. Just checked the code and that's what it saysm but I haven't tested it in a while.
davidfor is offline