04-16-2025, 04:12 AM
Annotations cannot be merged on an individual basis, because there is no way to uniquely identify them and correctly match them up between devices with 100% accuracy. There is no requirement that each device has an identical library, which means I can't assume the database IDs match up or anything of that sort. If an annotation is modified, the app could try to guess if the modified annotation on one device matches one of the existing annotations on the other device, but if the app gets this wrong, I doubt users would be okay with their annotations being completely messed up by an incorrect merge.
As far as files go, I reviewed the logic, and the code is not correctly looking for a newer version of a file when a two-way sync is used. I'll update this so it uses the last modified timestamp to determine which file to use.
Annotations are completely independent from files in terms of how they are stored. You can swap in a new version of a PDF and the annotations aren't impacted, which is why it's designed this way. So it's perfectly plausible that a sync could take a newer version of a file from one device, but annotations from the other device, depending on the song's last modified timestamp compared with the file's last modified timestamp.
Mike
As far as files go, I reviewed the logic, and the code is not correctly looking for a newer version of a file when a two-way sync is used. I'll update this so it uses the last modified timestamp to determine which file to use.
Annotations are completely independent from files in terms of how they are stored. You can swap in a new version of a PDF and the annotations aren't impacted, which is why it's designed this way. So it's perfectly plausible that a sync could take a newer version of a file from one device, but annotations from the other device, depending on the song's last modified timestamp compared with the file's last modified timestamp.
Mike