View Single Post
Old 06-17-2013, 09:25 AM   #102
eXistenZ
Connoisseur
eXistenZ for a long time would go to bed early.eXistenZ for a long time would go to bed early.eXistenZ for a long time would go to bed early.eXistenZ for a long time would go to bed early.eXistenZ for a long time would go to bed early.eXistenZ for a long time would go to bed early.eXistenZ for a long time would go to bed early.eXistenZ for a long time would go to bed early.eXistenZ for a long time would go to bed early.eXistenZ for a long time would go to bed early.eXistenZ for a long time would go to bed early.
 
Posts: 86
Karma: 17618
Join Date: Nov 2010
Device: Kobo GLO
Quote:
Originally Posted by davidfor View Post
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.
About this, storing these infos from the ereader into calibre automatically seems a great feature to me, but if this happens just after the connection of the ereader, if user has just hard resetted the kobo the store action risks to start to soon an overwrite the data stored in calibre with empty one from the reader (hope it's clear what I want to explain).

A solution could be to let the auto storing action from just after the connection, to just before the disconnection (from the Eject Device command), I don't know
if it is possible, or another solution is to double the reading position creating an OLD and a NEW reading position for each book, so at the connection of the ereader, data in the NEW are moved in OLD as a safekeper, only after that reading positions in the kobo DB are stored to NEW, doing so if the store action from device to NEW is accidental the real data are safe in OLD ready to be restored (once again, hope it's clear what I want to say).
eXistenZ is offline