Comments on: Enable “Save As” in OS X Mountain Lion

By: arumdev

arumdev — Wed, 06 Mar 2013 00:37:04 +0000

see my other post…

By: arumdev

arumdev — Wed, 06 Mar 2013 00:36:38 +0000

Dean Shepherd:

To restore the library folder to it’s rightful home (in fact it’s always been there, it’s just hidden), paste the following line into terminal and press enter:

chflags nohidden ~/Library/

job done.

I’m afraid I can’t help with problem 2.

By: Dean Shepherd

Dean Shepherd — Fri, 01 Mar 2013 22:52:01 +0000

Agreed. They’ve really emasculated scanning in Preview. In Snow Leopard it would pre-scan and select multiple objects automatically – no need to move crop lines around for each object. This was far in advance of any PC scanning software I use at work, even from HP.

Now, even with 1.8.2, Preview can’t even delineate a single object. I have to move the crop lines to select even a single object. This does not even match the basic software on my PC at work (which itself hasn’t had the HP scanning software been updated since 2008 or maybe 2009 – so long ago I forget).

Apple seems to be removing everything genuinely useful to people simply to add functions only the less intelligent tend to use. I think I need to go back to SL. Hopefully I can find a ay to do this.

I only upgraded to ML from SL because I bought the USB Fender Strat guitar and AppleStore said it was necessary to have ML installed. I have since read from other USB Strat users that SL is fine.

By: Dean Shepherd

Dean Shepherd — Fri, 01 Mar 2013 22:36:22 +0000

Hi. I’m new here.

I’ve got 10.8.2 installed. Are you saying the dodge described in this Article now works despite initial doubts/problems?

By: Dean Shepherd

Dean Shepherd — Fri, 01 Mar 2013 22:08:11 +0000

Just the job. Just what I needed to know.

However, to truly achieve Scott’s ‘god’ status, thou shalt tell me -

1) How to restore access to the ‘Library’ folder, and

2) How to restore all the advanced scanning functions in ‘Preview’ lost when changing from Snow Leopard to Mountain Lion.

Satisfy number 1) and I will release Steve Jobs from his eternal incarceration;

Satisfy 2) and I will anoint you as the one true god (for scott at least);

Satisfy 1) and 2) and I will be seriously impressed.

By: Herrin Larkan

Herrin Larkan — Tue, 26 Feb 2013 03:59:21 +0000

Thanks so much for this. It Works!

There’s a disturbing trend in Apples OS where they seem to be both over thinking the interface and simultaneously dumbing it down for beginners.

Here’s to hope they return to a more logical thinking process as they receive feedback from users.

By: scott

scott — Fri, 08 Feb 2013 22:10:23 +0000

oh my god. thank you.

By: adm

adm — Thu, 31 Jan 2013 14:38:14 +0000

CONFIRMED:

Although the original author hasn’t bothered to respond to the MAJOR bugs in the original article (as described in detail in the comments), this now WORKS CORRECTLY on OS X Lion (10.8.2).

Use it – it’s great.

By: Jenn

Jenn — Fri, 11 Jan 2013 17:05:47 +0000

Thank you – this was perfect and incredibly helpful!

By: Remco

Remco — Thu, 20 Dec 2012 12:20:53 +0000

It seems Apple has listened to the complaints, as 10.8.2 adds the option ‘Keep changes in original document’ in the Save As dialog. Thankfully it even seems to remember that you’ve disabled it.

I tested this and if this option in the Save As dialog is unchecked, changes are NOT written to the original file.
So unless I’m missing something here, Save As is working as ‘normal’ again.

By: Richard

Richard — Thu, 06 Dec 2012 15:48:36 +0000

Apple seems to be making steps backwards these days. Removing Save As and replacing with Duplicate is just plain dumb. Why “fix” something that isn’t broken? And the fact that Save As now makes changes to both versions of the file. How can this kind of crap get past the Apple QA process? Or do they even have one nowadays?

By: Thomas

Thomas — Sat, 29 Sep 2012 23:31:15 +0000

Sorry, but what is the real difference?

By: Gustav

Gustav — Wed, 29 Aug 2012 15:38:16 +0000

This is true, but even though it was always the way, it was very dangerous behaviour. There’s always the chance of accidentally saving when trying to press a different keystroke or you were in the habit of pressing Cmd-S because you were saving a lot in another document previously.

The new Save As… is worse because there’s no indication it did not behave as before.

By: Dah•veed

Dah•veed — Tue, 28 Aug 2012 17:49:52 +0000

The issue here is that you have to have intention aforethought. Many times folks don’t decide that they want to save the changes as a separate file and keep the original untouched until well into the project of making changes.

By: Longtime Mac

Longtime Mac — Tue, 28 Aug 2012 15:56:44 +0000

Macworld published an article about a month ago that addressed this. They had a good—but not free—workaround. Basically create a workflow in Keyboard Maestro that duplicates the document when you want to and closes the original without saving changes. A kludge, but it works. It may be possible to do this with Automator but I haven’t looked.

The comments are right, though, to point out that the new “Save As” command is destructive and will deliver surprising results to unaware users. Basically, I think Apple just gave us “old, unworkable folks” a pacifier so that we’d maybe not object to “Duplicate” so much. Bad news.