Hm - I just stumbled across a very inconvenient thing
:
If I get this correctly, then annotations are kept separately in a database. This database apparently uses the ${path}/${filename} as associating identifier.
When a file is renamed or removed,
all annotations are seemingly removed (i.e. disassociated) from the document, until it resumes its original position and name. (so one may never move a document one plans on continuing to work on - or at least has to remember its position)
What's worse is that the DB is not even updated when the file is moved with the file operations on the M92 itself.
OK - knowing this, one may work around this issue, but I think that is an important thing to fix (and it will confuse every customer that does not have the technical background information).
I think that _all_ information w.r.t. a file should be local to its position so that it is easily moved along with the document. Irex solved this issue by replacing every .pdf file by a corresponding directory into which they placed the document and all metadata. If the DB is an sqlite DB (is it?), this should be fairly easy to do (I see no need for a global DB, when you can have one per document).
(Adding it to the wishlist...
)
Update: I just saw that at least sketches (unsure about highlight annotations(?)) are kept in a hidden directory .onyx in the respective directory... so it's not all the way as bad as I thought in my initial shock... nonetheless, the contents do not follow any renaming/file moving... and it's not a good idea in situations where customers are not aware of this and may want to manage directories on their PCs rather than the reader itself... inadvertedly (seemingly) 'losing' their work
P.S.: Annotation export is somewhat broken in 1.7 - spaces of highlighted text are not exported (they are simply omitted
)