View Single Post
Old 05-10-2014, 04:02 AM   #513
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
Update to Kobo Utilities plugin - V1.6.6

I have just uploaded a new version of the plugin. This has two changes:
  • Change: When storing book status, use the status from the furtherest along copy if there are multiple copies. This is latest status, date or percent read.
  • Change: Make jobs DeviceJobs so they won't get run at same time as initial device jobs.

The first change will probably be most noticeable by people who have purchased a book from Kobo but have also sideloaded the epub version. What I frequently do is start reading the downloaded kepub but swap to the epub if I don't like the formatting of the kepub. When doing this, sometimes the store would keep storing the reading position for the kepub. This change should make sure the status will be stored for the copy that is actually being read.

The other change is because of a occasional problem with the automatic backup. I few people have reported that the backup was shown to be corrupted but the database on the device wasn't. I had this happen a couple of times as well. This was probably because the backup was done while the "Send metadata to device" job was running. That job could update the database so there was a risk that the copy was done while changes were being made. The change will mean that the automatic jobs the plugin runs will be run as device jobs and ensures the jobs are run sequentially. This will also mean that while the jobs are running, calibre will not allow the device to be ejected.

As usual, the update will be announced within calibre in a little while. And if anyone has any problems with it, please tell me.
davidfor is offline