Save backup files for each time we save a patch
It would be wonderful to have "versioning" when saving patches as we make changes. I'm thinking of having Unify save the existing patch as ".BAK1" when I save my changes to a patch... then ".BAK2", etc. so worst case, I could go back and rename one of the backups to revert patch changes.
An interesting idea. I'll think about it, but in the meantime you can implement this yourself by using "Save As" every time, and adding 1, 2, 3, etc. to the name each time.
@getdunne I thought of that, but this would result in a lot of redundant patches being added to the database, and would require a bunch of manual cleanup once you have the final one you want. And that takes a bunch more steps (save as, change name, save) than just clicking Save.
Good point -- my approach would result in extra database entries. I've added your suggestions to the to-do list.
As a workaround in the meantime we could save patches in something like OneDrive (or use a junction point to redirect that folder, as I have). OneDrive has versions so you could recover to a previous version of the patch if you need to.