Thread: [GUI Plugin] Annotations
View Single Post
Old 11-22-2015, 07:19 AM   #206
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 bopuc View Post
Hello,
Annotations plugin is at the very core of my calibre usage — my annotations are at the core of why I read — so thank you for the time and effort you put into this. Very much appreciated!

For the first time, without any change in my setup (calibre 2.44.1, annotation 1.4.3), I am suddenly getting this message when importing from my (same old) Kindle:
"Annotations from 5 books added to None"
Sure enough, they are not added to the Calibre database.

(They are however in the plugin's database… which I would love if you could confirm that that database is authoritative and persistent. Old versions of the plugin used it only as a temporary dump…)

I've checked the system logs and calibre isn't saying anything about it.

Any leads? Any more info I can provide to help figure it out?
Have you changed libraries? The "None" in the message is because the column the annotations is to be stored in has not been set. If you open the configuration dialog and press OK, it will fix this but it will default to the "Comments" field.

The annotations are in the database and should be written to the books when you next do a fetch from the device. Or at least that's what I think will happen. It's been to long since I looked at that part of the code.

I'll post a fix for this shortly. Plus the changes I posted as a beta in August and completely forgot about.
davidfor is offline   Reply With Quote