4 ms·
Yeah, I noticed this one too, when cropping a picture and saving it as a new file (in Preview). Both the original and the new one were cropped. A moment of pa
by Groxx 14y ago
Yeah, I noticed this one too, when cropping a picture and saving it as a new file (in Preview). Both the original and the new one were cropped. A moment of panic later, and I found the revert option in Preview, but only because I knew it existed.
Totally. 100%. Undesirable. I did not Save. I saved to a new file. The only option now appears to be duplicating before editing (bad) or hoping the application has an 'export' option which sidesteps this (also bad - export typically presents far more options than save-as).
- kalleboo 14y ago> duplicating before editing (bad) Why is this bad? edit: Why are people downvoting me for asking this question? I'm genuinely curious.
- prodigal_erik 14y agoIt requires me to decide whether or not I'm going to want to keep a change, before I've even started on it. Otherwise I have to plow through a big undo stack, even assuming undo is supported (and persisted) for everything I did.
- kalleboo 14y agoThere's a "Revert" menu item that reverts to the last opened state, and if you managed to close the file, there's Versions. The change is really confusing to long time computer users. I wonder if Apple could have avoided this confusion by changing the names of "Save" and friends to something completely different.
- Groxx 14y agoSince original the file is saved, there's nothing preventing you from closing the file. "Managing to" is as easy as closing the window with cmd-w or hitting the red dot. Previously you could say 'no' to the 'save changes' dialog that popped up reliably - now it's just gone and there's essentially no indication that you can fix it.
- kalleboo 14y agoLook at it the other way: With the old system, if you pressed "Don't save" to that dialog by mistake, you lost everything. With the new system, it's basically impossible to lose anything (the only way is if you don't notice for long enough that the old version gets reaped).
- Groxx 14y agoIf you know it exists. And how long until it gets reaped? (I honestly have no idea. probably long enough for it to not matter, though, I'll admit) I'll try another way too. You had unsaved changes. You chose 'save as', which you know makes a new file. Why would you want to save the current changes to both files, ending up with two identical ones? Filename aside, they're the same file, but one can be reverted and the other can't. That's what copy/paste/duplicate is for. edit: there are plenty of valid cases for this, but they're mostly specialty (saving stages of changes in e.g. design work). why would the average person under average use want to save-as and end up with two identical files?
- apawloski 14y agoNo idea why you were downvoted, I'm interested in learning about this too.
- Groxx 14y agoBecause it's a horrible UX paradigm to require. If 'Save As...' had never existed, it wouldn't be unreasonable, but it is (was) a reasonable behavior that every other system I'm aware of has maintained. This passive versioning thing is quite nice in some aspects, but it's very unknown with most people I've seen. They see a file changed, they assume it's stuck like that now and the original is gone forever. Why would they expect otherwise? Their unsaved file gave no indication of being saved. Every application they open it in, and everyone they email it to, will only get the most-recent version. Even the file-system doesn't tell you when you have multiple versions of something.
- kalleboo 14y agoI see it as part of the iOSification of OS X, to appeal to iPad/iPhone halo converts. My phone has never asked me if I want to "Save changes".
- Groxx 14y agoI like the feature, to be clear. I just think it's horribly executed, and the education side has been even worse. The problem is that they took something. Then they changed it, giving it multiple nearly-invisible modes it can be in, which changes from application to application (not all have a 'revert' option, even for versioned files). Then they didn't tell anyone. For instance. I just cropped this file. How do I know the original still exists? http://cl.ly/image/2L2X0x042W0N http://cl.ly/image/2L2X0x042W0N Here, I opened it in another application. Are there multiple versions? http://cl.ly/image/3Y1m3C2r1r2f http://cl.ly/image/3Y1m3C2r1r2f What about in the File menu? http://cl.ly/image/0F2o2H2i3Z2f http://cl.ly/image/0F2o2H2i3Z2f Finder? http://cl.ly/image/1C0S3z3Z0q30 http://cl.ly/image/1C0S3z3Z0q30 or http://cl.ly/image/463p0O1I3q1C http://cl.ly/image/463p0O1I3q1C or http://cl.ly/image/1F191E3b3U1W http://cl.ly/image/1F191E3b3U1W ? (edit) Oh, cool - there's a "Versions" column. Maybe that has it: http://cl.ly/image/2703273U3z2U http://cl.ly/image/2703273U3z2U This is bad.
- thatjoshguy 14y agoAlways assume that every change you make is saved automatically, much like cutting down a physical photo. If you still want the original photo, and another cut down version, you would use a photo copier to Duplicate the original, then cut the copy.
- abduhl 14y agoI often find myself making a base model and then iterating down different paths using saved as on the fly with no prior knowledge of the number of iterations (duplicates) I will end up with.
- dubya 14y agoThis behavior wasn't really introduced with "Save as..." in ML. In Lion, if you rotate a page in the middle of a PDF, then quit and reopen the file hoping to undo the rotate, it will still be rotated. Fortunately, it was someone else's presentation where I first saw this. Anyhow, ML isn't doing a "save" and "save as..." now; it had already done the "save" part. Apple really should do a better job explaining this, but it's most likely not consistent across all apps. Does XCode even do this now? It reminds me of the preferences behavior where you make your changes and that's it, rather than requiring you to hit an "OK" or "Apply" button as in Windows.