Q: What happened to Save As?

"• Go back to the original open document"

and

"• Use the top menu to revert to its original state"

I never saw the need to do that.  If you don't edit the file since duplication, you should be able to just close it off.

"• Close the original"

Only when I need to, thanks.

—tonza

If you don't edit the file since duplication, you should be able to just close it off.

Your acute inability to read is astounding. I mentioned my reasoning - twice. Here they are again.

If you've made changes to a file and want it to branch off to a new document while retaining the original unaltered file,

when you are trying to save an open document, which has changes to it, to a new name without the original being altered.

Duplicate does not allow for this kind of workflow. If you've made changes and then decide against saving the original that way, and would rather have those changes in a new document, you must go through the steps to revert the original. That is something you never have to do with Save As. The open document simply becomes the edited file with the new name, and the original is closed with no changes saved to it.

Thanks for the echo, Kurt.  Your description is exactly correct.

It is laughable to think about the consequences of this work habit: "I tend to leave documents that I have duplicated open for a while in case I need to refer to them later.  Only when I'm fairly sure I am OK with not having to go back do I close them off."

As someone who works with dozens, maybe hundreds of documents daily, it is awe-inspiring to imagine what it would be like to look over his shoulder and watch him do his work.  What is "a while" ... a few minutes?  A week?

If I am ever fairly sure I am OK with never having to go back to something, then I don't even consider saving it, I throw it in the trash!   Why save any documents at all?  Why not just leave them all open and unsaved, scattered all over your computer screen? 

OMG.   Woody Allen had a way to describe that mentality but I won't repeat it here.

That merely means you are making a duplicate of an unsaved file.  This doesn't change the arguement one bit.

And please, don't tell me that I can't read.  Otherwise, I'll just choose not to read your comments.

—tonza

"It is laughable to think about the consequences of this work habit..."

And I suppose what you do by habit is any better?

"As someone who works with dozens, maybe hundreds of documents daily, it is awe-inspiring to imagine what it would be like to look over his shoulder and watch him do his work.  What is "a while" ... a few minutes?  A week?"

I often don't have to do anything.  For example, if I go to the Finder and trash the original when I choose to, and then open the app again, since the document no longer exists, the app won't try and open it.

And who are you to judge how I work?!  Dunno about you but I am not in the habit of losing data.  Data reconstruction is more costly than fiddling around with a user interface.

—tonza

That merely means you are making a duplicate of an unsaved file.  This doesn't change the argument one bit.

As usual, you can't refute one bit of someone's statement, so you dismiss the post without a single thing to contradict it.

AGAIN, I've opened an existing file, I make changes to it, I later decide I don't want those changes to be saved to the original, I chose Save As and it automatically becomes the file containing the changes, the original is closed, unaltered. I do not need to even think about going back to revert what Lion will so happily save for me against my wishes.

Do that with Duplicate as easily. It's impossible.

Duplicate before you make a change.  Otherwise, any changes you make will be saved on the file you didn't bother to duplicate.

The premise of Lion's Auto Save feature is that what you change in the app will end up in storage, regardless of what happens to your document in system memory.  As I explained before, auto-saving is reliable enough that even killing a process doesn't stop a file from being saved.  And that's the entire benefit of Lion—it is better designed than Snow Leopard in being a failsafe system.

—tonza

You are truly hopeless, tonza. Any explanation, no matter how valid, is thrown aside simply because it conflicts with your opinion.

Duplicate before you make a change.

And just to clarify - again - you indeed can't read. I said:

I later decide I don't want those changes to be saved to the original...

What do you not understand about such a straightforward comment? Since I neither have a crystal ball, or other means to see into the future, I don't always KNOW ahead of time I might not want to alter the original I've been working on for the last hour. But apparently, you do.

You know you're about to make changes!  Don't tell me that you need a crystal ball for that!

OK, this discussion has degraded down to a point of conflict of interest. There's nothing further I can say.

Happy travels.

—tonza

Kurt, you have to ignore most of what that guy writes.  He doesn't read what you or I or anyone selse has written nor does he think about what was written before responding.  He responds before reading, before thinking.  He's just quick on the trigger to rephrase his strongly-held opinion without considering any possibility that he could be mistaken or learn from someone else.

As far as I'm concerned, I never know whether I'm going to need something in the future.  If I could see into the future that way, I would just point my crystal ball at apple.com and explore the operating system we will have in 2015.  That would tell me if this thread will have gotten the attention of people who can listen, think and respond.  By 2015, Mr. Tonza should have a tens of thousands of open, autosaved documents on his desktop and the world's largest collection of Templates.

Oh for lordy's sake, he really can't read, can he?

He doesn't read what you or I or anyone selse has written nor does he think about what was written before responding.

That pretty much sums it up.

You know you're about to make changes!

Of course I know I'm making changes!!! One last time, READ, if you're capable of reading AND comprehending.

I don't always KNOW ahead of time I might not want to alter the original I've been working on for the last hour.

Sir, you deserve all the credit for the degredation.  Happy trails to you too.

tonza wrote:

 

Wow!  That's one **** of a pickup!  How'd you come across that?!

 

;-)

We are urged to read the License before installing every app but we may also read it later (or before if like me you are thinking that consumer is a true job).

Clicking open the page below.

Yvan KOENIG (VALLAURIS, France) mardi 14 février 2012

iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.3

My Box account  is : http://www.box.com/s/00qnssoyeq2xvc22ra4k

I guess that you will be glad to read this page :

http://www.bloomberg.com/news/2012-02-16/apple-speeds-mac-mountain-lion-operatin g-system-to-challenge-windows-8.html

Yvan KOENIG (VALLAURIS, France) jeudi 16 février 2012

iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.3

My Box account  is : http://www.box.com/s/00qnssoyeq2xvc22ra4k