4 ms·
The most annoying thing for me is that the idea of take something similar, make my changes to it, and save it under a different name only mangles the original f
by godshatter 4y ago
The most annoying thing for me is that the idea of take something similar, make my changes to it, and save it under a different name only mangles the original file in today's world.
- Our_Benefactors 4y ago“Save” vs “Save as” is such a terrible convention…
- TeMPOraL 4y agoIt is, because arguably the more common case is wanting to save a snapshot under a different name and continue editing the original. "Save as", unfortunately, does the opposite.
- godshatter 4y agoI, personally, want save to act like committing a transaction. I don't like making changes to something and having every key typed or item clicked on be an immediate change to the file. The common case for me is to start making changes, then save them when I'm ready, sometimes as another file name. At least 30 years of this behavior has been ingrained into my workflows. We have undo, but I'd also like to have a revert changes option that acts like rolling back a transaction. The simple rollback is to just close the file without saving, but that doesn't work if every change big or small is a commit.