Linked by Thom Holwerda on Mon 6th Aug 2012 13:16 UTC
Mac OS X How this passed through Apple's Mountain Lion testing is beyond me. "If one edits a document, then chooses Save As, then BOTH the edited original document and the copy are saved, thus not only saving a new copy, but silently saving the original with the same changes, thus overwriting the original." Just goes to show: do not mess with my ability to save my stuff. There is no one-size-fits-all for this kind of delicate stuff.
Permalink for comment 529900
To read all comments associated with this story, please click here.
file versioning
by henderson101 on Mon 6th Aug 2012 15:38 UTC
Member since:

*le sigh*... all files are now versioned in OS X. If you autosave a bunch of changes, the versions of the previous document is saved. "Save as" is saving the current document under a different name. I've never used "Save as" under any OS to duplicate the functionality that we seem to be having issues with here? Why? Because I religiously hit save (ctrl+s or whatever) every couple of minutes. The current document on disk is the document I'm duplicating. Your usage may vary, obviously.

The issue here is the workflow. It's that people are lazy and rely on apps not crashing and losing your work. Having lived through Acorn, Amiga, Classic Mac OS and Windows 3.1, I don't think anyone should make that assumption. Nothing like watching the OS get a GPF and your work sailing in to the ether.

Reply Score: 4