I can't support adding a file/blank page/template in the page ordering UI and not modify the original file. So I'm a little confused by what you are suggesting. I will add a warning when the save is going to impact songs that share a file (I've already added the code for this, just need to test it), but otherwise if a user utilizes those features, it's going to modify the original file. If you all truly believe I should warn the user that the changes they have made are going to modify their file even when that file is only used by a single song, I can do that, but I'll have to design it so that the warning has a "Don't warn me again" type option so that this doesn't become annoying, which it would probably would be for the vast majority of users. Alternatively, I can add an optional setting that users can enable to warn when a file will be overwritten, although I don't really see much value in that. I should mention again - if you insert a file into another file, and tap Save, the file that you added is placed at the end of the PDF, but the page order is updated to put the new pages where you inserted them. This means that this has no impact on existing annotations, link points or smart buttons (as the song editor will adjust everything to account for the new page order). So this is not a destructive action that will completely mess up a file beyond repair or anything of that nature. You could remove the new pages and then use the "Update file with current page order" option to permanently remove the pages that were added if needed.
I can also just default to saving a file under a new name if it's modified, but in the past I would modify users filenames, and they got really irritated by that. So I imagine if I started doing this, I imagine many users would be upset by their files being renamed without them knowing it. I could have an optional setting that says something like, "Prompt for new name if file is modified" or something of that nature which kind of doubles as a warning, but I just don't know if that's really warranted in the case where a file is only used by a single song.
Mike
I can also just default to saving a file under a new name if it's modified, but in the past I would modify users filenames, and they got really irritated by that. So I imagine if I started doing this, I imagine many users would be upset by their files being renamed without them knowing it. I could have an optional setting that says something like, "Prompt for new name if file is modified" or something of that nature which kind of doubles as a warning, but I just don't know if that's really warranted in the case where a file is only used by a single song.
Mike