Thread: [GUI Plugin] Annotations
View Single Post
Old 10-20-2020, 10:52 PM   #774
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 UMNiK View Post
Kindle Paperwhite 2018 with sideloaded kfx (matched in calibre).

Seems to fail in a most curious way:
Code:
DEBUG:   64.2  Book on device title: 'Legacy of the Aldenata – 02 – Gust Front'
DEBUG:   64.2  Kindle:get_active_annotations()
DEBUG:   64.2  ParseKindleMyClippingsTxt ERROR: Error trying to read clippings file: name 'file' is not defined
DEBUG:   64.2   Number of entries retrieved from 'My Clippings.txt'=0
DEBUG:   64.3 AnnotationsAction:fetch_usb_device_annotations(DEBUG: []) 
DEBUG:   64.3 AnnotationsAction:fetch_device_annotations(Amazon Kindle) 
DEBUG:   69.7 AnnotationsAction:fetch_device_annotations(INFO: <p>Unable to find any annotations on Amazon Kindle matching books in your library.</p>) 
DEBUG:   71.5 AnnotationsAction:shutting_down()
What I tried
  • Deleting My Clippings.txt and associated sdb
  • Reinstalling the plugin (after deleting the old config in AppData)
  • Running on newly transferred and annotated books that created a fresh My Clippings.txt

I know it kinda worked in September (had to manually match up books, but at least it gave me the option to do so), but I'm not sure what could have caused it to break now (I assume the move to Python 3 couldn't break it this badly).
I'm not sure why you think that. The changes needed for any of these plugins to work in Python 3 were enough that most were completely broken and didn't load at all. Fixing that part was generally easy, but there were a lot of subtle things that meant they looked like they worked, but didn't actually work.

The above is a Python 3 problem. Fixing that bit is easy, but, it is going to be broken elsewhere. Looking at it, I have not migrated the code in the Kindle or Tolino parts of the plugin properly. I'll have to fix that. I can't test the Kindle parts propely, so I will post a beta when it is ready.
davidfor is offline   Reply With Quote