06-27-2021, 05:44 PM
It's important to understand the distinction between different types of file conflicts in MobileSheetsPro, because while there isn't a one-to-one correlation with files and songs, you can certainly end up in situations where you have two files that happen to have the same name but are different versions of a song. For example, let's say you have multiple versions of the song "Yesterday". When you import yesterday.pdf, if you've never imported that file name before, there will be no conflicts and everything will proceed smoothly. However, if you now import another yesterday.pdf, MobileSheetsPro will recognize that there is already a yesterday.pdf in the storage location, so it asks you what you want to do about it. The companion app has been made a little smarter about this, so it will first ask you if you are actually trying to do a file swap instead of just importing a new file. If you say no, then you have to decide how to handle the file conflict:
1) Overwrite/replace the existing file (this would mess up the first song you created that used yesterday.pdf)
2) Rename the file (so that there is no longer a conflict)
3) Update the existing song with the new file (this is basically the same as performing the swap file operation)
So you can see here, that just overwriting and replacing the existing file is not always what you want to do. That's why I have to display this conflict dialog - if I just assumed you wanted to update the existing song, that would delete the first version of yesterday.pdf you imported, and you'd probably be pretty unhappy about that. If I just created a new song with every file import and you were just trying to update an existing song by reimporting a new version of an existing file in the library, then you'd be upset about that too. I think that dialog confuses a lot of people though because they are thinking of things either in terms of just songs and not how the files used by those songs are stored, or they think there is a one-to-one correlation of files to songs so if they import a new version of a file, they just assume it should update the existing song in the library. With the "Create Snippet" feature, there could be 50 songs in the library all sharing the same file, so if you update that file, it's going to impact 50 songs potentially.
Mike
1) Overwrite/replace the existing file (this would mess up the first song you created that used yesterday.pdf)
2) Rename the file (so that there is no longer a conflict)
3) Update the existing song with the new file (this is basically the same as performing the swap file operation)
So you can see here, that just overwriting and replacing the existing file is not always what you want to do. That's why I have to display this conflict dialog - if I just assumed you wanted to update the existing song, that would delete the first version of yesterday.pdf you imported, and you'd probably be pretty unhappy about that. If I just created a new song with every file import and you were just trying to update an existing song by reimporting a new version of an existing file in the library, then you'd be upset about that too. I think that dialog confuses a lot of people though because they are thinking of things either in terms of just songs and not how the files used by those songs are stored, or they think there is a one-to-one correlation of files to songs so if they import a new version of a file, they just assume it should update the existing song in the library. With the "Create Snippet" feature, there could be 50 songs in the library all sharing the same file, so if you update that file, it's going to impact 50 songs potentially.
Mike