Quote:
Originally Posted by Purple Lady
So if they can't be turned off and they also get set and restored by the find-duplicates plugin, how do you know what set them if you add this to CC?
|
Perhaps I should start at the beginning.
Temp marks are a feature of calibre that allows you to mark individual books for the life of the calibre session. Marked books are shown with a push pin.
Find duplicates uses marks internally for various things, one of which is books that are not to be considered duplicates (IIRC). For various reasons that plugin restores those marks when it restarts. This behavior is discussed in
https://www.mobileread.com/forums/sho...d.php?t=230724 and
https://www.mobileread.com/forums/sho...d.php?t=232807, amongst others. To my knowledge find duplicates is the only "thing" that restores marks. Note that it does not restore any marks other than its own.
The proposal here is to have CC optionally mark books where CC's read information was different from calibre's and therefore synced from CC to calibre during a connect. The intention behind the change is to provide a hint that you might want to update the metadata for books that you have read. For example, you might want to change the rating, update a tag, change a comment, or something else.
If you have marked other books for some reason during the calibre session or if you use find duplicates and it has marked other books, then the marks will intermingle. There are two solutions if this behavior is not acceptable:
1) Clear all marks before connecting as a wireless device.
2) Search for the mark of interest. CC's marks will be named something like "wd_read_synced", so the search would be "marked:wd_read_synced" instead of "marked:true".