Quote:
Originally Posted by sweth
Update: after some more playing around I noticed that the initial resolved path map is based on what the current search filter in Calibre is returning; was that always the behavior? Because the plugin requires you to select a book to add unmatched annotations to, I have an annotations dummy ebook file that I've created in Calibre and whenever I add annotations, I've (when I was doing this before w/ my old Paperwhite) searched in Calibre for "annot" and then selected that dummy ebook and run the plugin, so the initial list of books that the plugin sees is just the four books that match "annot". I tried again with no search filter applied in Calibre, and after a few minutes of hanging, the plugin output thousands of lines of debug output--but then ended the same way as above, w/ a clippings file read error and then concluding that there were no annotations.
|
Sorry, I made a change with how I opened the file and didn't check that it was compatible with Python 2 and hence calibre 4.28. It was just rearranging where the UTF-8 decoding was done. I have reverted this in the attached beta. That should fix the My Clipping.txt errors.
For finding the books, I would not expect that the current search would affect this. Using a virtual library probably would, but, I haven't tried this recently. I haven't change anything in how the books are found recently. The betas have a change in how the matching is done, but, that happens later. Can you try the attached beta an send me the full debug log?