[Zubersoft]

One option would be - if I detect that the song has annotations on pages, I force the chord pro file to be that many pages regardless of how many pages would be rendered normally. At least that way the annotations could be reached. The annoying part is that if the annotations are then changed, I will have to check each time to see if pages need to be removed and handle that accordingly. If a chord pro file is one page, but there are annotations on page 2 and 3, and the user removes all annotations on page 2, I then have to change all annotations on page 3 to page 2 and adjust the page length, etc. It certainly is tedious and introduces the possibility of bugs, but if you guys prefer that, I can certainly do it. I could also just leave blank pages in place up until the last page containing annotations, which is probably a simpler solution that is less error prone.

If it's just better to prompt to accept that the annotations will be deleted from non-visible pages after the file swap occurs, I can do that.

Mike