4 ms·
My biggest problem is that Apple is not explaining these changes. With the original Save/Save As, the concept was easy to understand after someone took 30 sec
by crazygringo 14y ago
My biggest problem is that Apple is not explaining these changes.
With the original Save/Save As, the concept was easy to understand after someone took 30 sec to explain it to you. You knew exactly what was happening.
But with Apple's new changes, Apple has made autosave and versions the new paradigm (awesome), but they've done a terrible job at explaining how to do anything but that.
How do I edit something and then save that edit as a new document without affecting the original? If I copy a file, does the whole version history get copied too? What if I send it to someone? What if I want to delete the version history period? What if I want to "duplicate" a file but not save it anywhere, because I just want to mess around with changes for a while?
I've been using Lion since it came out, and I don't really know the correct answers to any of those questions.
- X-Istence 14y agoThe version history is stored by the file system and not by the file itself. If you copy the document you don't store any of the version history and you can't revert (from my experience). Also, if you send the file to someone they get the latest changes, they don't get any history... the history is snapshots made by the OS much like Time Machine does for backups, except it is done every so often automatically (auto save) and not to an external drive. The only real cock-up is the Save As. Save As should save the new file, and revert the old file back to what it originally was (the last time I explicitly saved, not the spot that auto save last saved). If you want to modify a copy of the file, before you start your modifications you simply choose File -> Duplicate and it opens the same document but with a different name. When you save that one it will have an entirely new history associated with it. The fact that it is a file system feature that is baked into the OS means that all apps can take advantage of it if they want and the overhead is small. It also means that apps no longer need to keep notes about what modifications were done to what, instead being able to rely on the auto save feature. The other nice thing is that since it is not part of the document and is outside of it, data leakage is much less of an issue than with other file formats such as Microsoft Word where recovering previous text is rather simple and can lead to data leaking that you wouldn't want leaking.
- ktizo 14y agoIf you want to modify a copy of the file, before you start your modifications you simply choose File -> Duplicate and it opens the same document but with a different name. What if you only decide that you want to save as a different file after you are half way through your modifications?
- pyre 14y agoThat's not the Apple Way(tm). Please conform to the Apple Way(tm) when interacting with all Apple-branded devices please. ;-)
- batista 14y agoYes, very intelligent.
- jkestner 14y agoWhen you choose Duplicate on an edited file, you're given the option to Duplicate and Revert the original file. Handy.
- X-Istence 14y agoThat is not the case, at least not with TextEdit ... when you choose Duplicate you get two files with the same contents. You can then save the duplicate as you wish, and revert the old one back to when it was opened using File -> Revert -> Last Open.
- rsfinn 14y agoThat's how it worked in Lion, but Mountain Lion behaves differently -- you get the duplicate with its file name selected, so you can rename it, but the original stays modified unless you think to immediately pick "Revert to last saved version". I actually liked the Lion behavior better. (Now I wish I'd had the chance to try out the Mountain Lion beta before release, so I could have filed a bug for this.) That's what we get for everyone complaining about the lack of "Save As"...