| News | Features | Interviews |
| Blog | Contact | Editorials |
| OS X Mountain Lion: data loss via 'Save As' |
| By Thom Holwerda on 2012-08-06 13:16:11 |
| 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. |
|
| You need to use duplicate instead |
| By someone on 2012-08-06 13:32:08 |
|
I was always under the impression that Save As is just an alias for the Duplicate command introduced in Lion, but I guess that's not the case. In any case, Duplicate does inherit the Cmd+Shift+S shortcut from Save As. Honestly, I think the best course of action for Apple is for them to rename the new Save As command to something else, so that people are not confused. Edited 2012-08-06 13:34 UTC |
 - Score: 2 |
| RE: You need to use duplicate instead |
| By CapEnt on 2012-08-06 13:41:53 |
| It's not a bug, it's a feature! |
| - Score: 10 |
| Or... |
| By thavith_osn on 2012-08-06 13:41:58 |
| It's just a bug and will be fixed... |
| - Score: 2 |
| Probably Auto Save |
| By mango on 2012-08-06 13:52:33 |
|
Save as is not deleting your info. Auto save is saving you changes over the original. If you make changes to the original document auto save will save your changes. Then when you click "save as" you get a new copy of the document with you changes. |
| - Score: 7 |
| RE: Or... |
| By Tony Swash on 2012-08-06 13:53:35 |
|
Being a bit conservative having accumulated lots of set habits over decades on computers I never took to the Duplicate function, although I understand why it might be a clearer way to do things to new users, so I used the technique shown here http://www.tuaw.com/2012/07/29/g... to permanently replace the Duplicate menu item with a 'Save As...' So this bug is a bummer, let's hope they get if fixed in 10.8.1 |
| - Score: 2 |
| RE: Probably Auto Save |
| By Tony Swash on 2012-08-06 13:58:56 |
|
Well spotted. This shows you how to disable Auto-Save on a per app basis, does anybody know if this works in Mountain Lion http://osxdaily.com/2012/07/11/d... |
| - Score: 3 |
| RE: Probably Auto Save |
| By jessesmith on 2012-08-06 14:10:12 |
| That is still horrible behaviour. Auto-save should not over-write the original document, it should be saving changes to a hidden file which can be recovered in the case of a crash. Over-writing a document without the user saying so is a terrible idea. |
| - Score: 12 |
| RE[2]: Probably Auto Save |
| By MOS6510 on 2012-08-06 14:31:32 |
|
I have a Numbers spreadsheet, added some stuff, saved it, did a sort on all data (few hundred lines), quit, opened it the next time only to discover all my data messed up. Lucky I had a recent backup. (this was pre-Mountain Lion) |
| - Score: 3 |
| file versioning |
| By henderson101 on 2012-08-06 15:38:01 |
|
*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. |
| - Score: 4 |
| RE: file versioning |
| By Neolander on 2012-08-06 16:07:12 |
|
+1 The point of Lion's auto-save feature is to abstract the intricacies of the memory hierarchy away from the user. You cannot edit a vulnerable in-RAM copy of a file for hours anymore, instead you edit a periodically updated on-disk copy that loses only a few minutes worth of work in the event of a hardware failure. That's actually a very good thing, as it voids the need for most people's hysteric manual saving disorder, replacing it with a superior versioning mechanism ! Really, I'd change a few details myself, but it seems to me that Apple got the big picture right for this feature. |
| - Score: 5 |
| News | Features | Interviews |
| Blog | Contact | Editorials |