Comment from mamablair
IMO, the key for using Save As properly is to always make sure you first do a regular Save, so the current document is truly saved. Then, and only then, Save As under a different name. This worked...
View ArticleComment from David Emme
I agree. And frankly, I like the "old" saving behavior, which is part of why I'm still on 10.6I think part of the problem under discussion here is that Apple shot themselves in the foot by bringing...
View ArticleComment from Marc
Mike, thanks for this. "El Aura" seems to be one of these Apple loyalists who will brook no criticism, as if 100% of what Apple does is completely perfect and anyone who voices a concern is just a...
View ArticleComment from Marc
"Save As" has worked the same way for as long as I've been using computers, which is a long time. One develops muscle memory for doing certain tasks. You can't just change overnight. Also, how many...
View ArticleComment from Mike
"So when Lion introduced Versions and AutoSave, I immediate disabled them."May I ask how you accomplished this? I would be overjoyed to find a method for disabling Auto Save and Versions that did not...
View ArticleComment from Mike
1) You asked a specific question about Duplicate. I gave a specific answer. What's the problem? Save As in Mountain Lion does not function in the same way it does in Snow Leopard (and earlier...a total...
View ArticleComment from Tom Robinson
The rational argument is that Apple likes to keep things looking as simple as possible to the end user, and this includes having the bare minimum of preferences. A new preference here, a new one...
View ArticleComment from Mike
If Auto Save and Versioning are the default, as I propose, then the "end user" has to do exactly nothing for them to work exactly as advertised.Your fears about "complicating" the Mac experience are...
View ArticleComment from Mike
"Bottom line: new functionality that requires the user to change his or her behaviour will annoy 90% of all users because 90% of all users are incapable of any behavioural change."Again I point out --...
View ArticleComment from rasmusdotse
I'm surprised Apple managed to create a stupid autosave, since there are several very useful and rational models for autosave in professional, but often expensive software.One model for autosave is...
View ArticleComment from MoT
Agreed. This has to be the most ignorant thing Apple could have ever done. It's the equivalent of switching the brake and gas pedals and telling your users to "get over it"
View ArticleComment from MoT
I've held off of upgrading to Lion or ML for the very reason that the "save" function has been crippled. The idea that I first of all have to save a duplicate copy BEFORE doing any possible changes,...
View ArticleComment from George
Apple should have left everything exactly as it was but have the document autosave for versions, that's all. And the option to turn it on/off... and when enabled the save item would be greyed or...
View ArticleComment from samadore
Having not upgraded beyond Snow Leopard, I cannot choose a side in this debate yet. I have however been reading numerous articles on the issue in an attempt to prepare myself. I'd like to commend and...
View ArticleComment from David Morrison
I think you are being a bit optimistic here. VMS file names had a version number as part of the name. Each time you edited a file, the default was to save a new file with the same name and the version...
View ArticleComment from Richard Fairbanks
Thank you, Matt, for such a vital article!!I commend Apple for restoring “Save As . . . ” (and adding the two System Preferences/General prefs) as a means to honor the dictum:“Never alter a user’s...
View ArticleComment from Michael Warshauer
Yes; what ever happened to "Macintosh-the computer for the rest of us."?
View ArticleComment from Jason
Whoah! The rest of this article made my head spin, which is, by no means, the author's fault. Methinks I'll stay with Snow Leopard a little longer after all:(
View ArticleComment from Jason
OMG! I never noticed that black dot in the red close button before. After how many years? It's so useful, so unobtrusive and so frustratingly Apple - elegant to the point of obscurity:| It's like their...
View ArticleComment from Al
I read this nicely thought out article. Now my head hurts. Where's my coffee?
View ArticleComment from Padre Cohen
Mountain Lion's document handling is a solution in search of a problem.
View ArticleComment from Peter Waslowski
I was also concerned about the Save As behavior. Having read your excellent article I understand what's going on. Thanks! Now please tell me if I am missing something: When I save a doc via Save As…...
View ArticleComment from Slim
It seems that way as you suggest, if autosave continues to function the way you would expect (save your "old" document when you do "Save as"), so you haven't really lost the "old document" when you...
View ArticleComment from William H Boyd Jr
I just discovered that, with the "Ask to keep changes when closing documents" option checked, if I edit a file on a network volume, as soon as I make a change to the file, the black dot appears, as...
View ArticleComment from Dah•veed
You can return the Save As… command to the File menu with it's traditional key command by adding it as a Keyboard Shortcut. By using the traditional key command I am not aware that it effects other...
View ArticleComment from Adam Engst
Very cool! That does seem to work in TextEdit, Preview, and Pages here.
View ArticleComment from joaquin
Thanks, Peter Waslowski, for keeping attention on the major change in SaveAs: it no longer discards changes to the originally opened document since the last Save. Thanks, Slim, for calling attention to...
View ArticleComment from Matt Neuburg
See now http://tidbits.com/article/13284. This problem is solved.
View Article
More Pages to Explore .....