Q: Disable autosave

You are warned that the file has been edited. Closing it will save the edits, unless you choose to revert.

I question why you would copy a file unless you are happy with it, in which case you want to save the edits!

File>Revert brings up this dialogue:

And you post all of this to once again IGNORE the fact that Duplicate takes at least three more steps as Save As. Four if you need to revert the original after the Duplicate command if it has changes. Something you never have to do with Save As.

This time I will not reuse your words because I don't trust in any kind of god.

Ni dieu ni maître !

It seems that you are unable to read a message of 60 words ?

I repeat what I wrote :

Wrong

Open a doc

duplicate

close the original if you want.

the changes made on the duplicate will not apply to the original

If you want to save them in the new file you may do

If you want to save them in the original you may do too.

But it seems that it's too simple for some minds here.

This scheme isn't describing what you are dreaming but what may be done to achieve your goal with the existing app because I guess (I highlight guess to be sure that you will not read hope) that hope to retrieve the old behavior is near zero.

If you open a doc, duplicate it then close the original immediately, there will be no change saved in this original.

You will work on the replicate.

And then you will be free to :

save nothing

save in a new file

save using the name of the original file.

It's what you were able to achieve with the old scheme:

open a doc

work on it

save nothing

save in a new file

save in the original file.

I repeat what seamingly you didn't understood :

nothing is saved in the newly created replicate as long as you don't explicitely ask the app to do.

You will have some difficulties to convince Apple engineers that there is a huge difference between the two schemes, one which is dead and one which is well and alive.

Yvan KOENIG (VALLAURIS, France) dimanche 30 octobre 2011 16:11:54

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

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community

that hope to retrieve the old behavior is near zero.

Finally, the reason for all of these repeated answers. You believe they will never come back, so you feel it is necessary to educate everyone on the new workflow.

However, unless you are an Apple engineer in charge of such things, you cannot know that any more than I. Which makes such statements speculation at best.

one which is dead and one which is well and alive.

Wrong. The only software where it is "dead" is in Apple's own products. They need to wake up and do what the customer wants, not just what they want.

As I already wrote, you are perfectly wrong.

They are free to do what they want, not what some customers want.

You are dreaming in your cloud.

I have feets on earth.

Yvan KOENIG (VALLAURIS, France) dimanche 30 octobre 2011 16:42:56

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

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community

They are free to do what they want, not what some customers want.

Any company that does not listen to their customers are beyond foolish.

I have feets on earth.

And the manners of a troll. You have nothing to defend your statements with, so you resort to name calling and insults.

I'd like to throw in the suggestion not to answer to Yvans posts any more. I guess he's just poking around to create the biggest possible mess. The way I see it, he's insulting, pulling the discussion off the actual point and preventing others from posting. I'm tired of that.

I couldn't agree more. His only involvement here seems to be to deliberately agitate.

Back on topic, there might be a suggestion to Apple which they might be able to pick up. Since they want to move towards iOS where all editing is instantly saved (like working in a FileMaker database) I see the chances of a disable-able Autosave not very high. However, what would be a improvement would be an option to turn on/off the good old dialoge box that shows up when quitting an unsaved document.

By this way we could avoid the revert-process and just discard changes. This wouldn't solve the problems that users have with large documents or the clumsy duplicate-feature. But at least it would solve much of the workflow problems and the unwanted-data-overwrite issue.

Just re-enable the "Save changes?" dialogue.

Since they want to move towards iOS where all editing is instantly saved (like working in a FileMaker database) I see the chances of a disable-able Autosave not very high.

That's what I, and anyone I know who uses their computers for production work are afraid of. A desktop computer can never by used like a tablet (iPad) and get any reasonable amount of work done. They are two very different types of computers with very different uses.

papalapapp wrote:

 

Since they want to move towards iOS where all editing is instantly saved (like working in a FileMaker database) I see the chances of a disable-able Autosave not very high.

I would argue that since third party applications must be altered in order to take "advantage" of Autosave and Versions then Apple should be able to make those "features" optional in Apple applications.

I would argue that since third party applications must be altered in order to take "advantage" of Autosave and Versions then Apple should be able to make those "features" optional in Apple applications.

Which actually isn't just an argument, but is a fact. Vendors have the option of using the traditional workflow, or the new one. Graphic Converter already has that option, and by default, Apple's new method is off. All third party vendors have the same ability to make which workflow you prefer optional.

So why is this such big stink? For users of Apple products, it is widely disliked with Final Cut X Pro, the latest iLife software, etc. Not having a choice is driving some users nuts. I also feel it's necessary to make this dislike known early on to at least let Apple know that not everyone ever wants to see this new workflow become the ONLY one they allow.

Kurt Lang wrote:

 

Since they want to move towards iOS where all editing is instantly saved (like working in a FileMaker database) I see the chances of a disable-able Autosave not very high.

That's what I, and anyone I know who uses their computers for production work are afraid of.  ...

Exactly.

If it was such a great feature, it would be accepted, used and loved although it could be turned off.

papalapapp wrote:

 

I'd like to throw in the suggestion not to answer to Yvans posts any more. I guess he's just poking around to create the biggest possible mess. The way I see it, he's insulting, pulling the discussion off the actual point and preventing others from posting. I'm tired of that.

This would be a good idea, since Yvan does not "answer" the posts that make him uncomfortable. He just ignores them, and hopes no one will notice.

But for me, I just can't resist playing with Yvan...it's so much fun!

For the third time, Yvan:

1) What is wrong with making Auto Save/Versioning the default, but including the option for expert users who so choose to disable it? Please describe, in detail, the specific disasters that will result from this.

2) How, exactly, to you defend a "feature" that renders a program unusable (the example of the Keynote presentation with large files imbedded that brings up a spinning beach ball every few seconds during Auto Save)? Why is this perfectly OK with you? What alternative do you propose for this user? (And PLEASE don't say PowerPoint!)

As long as you keep ignoring these questions, I'll keep reminding everybody here of what a chicken-heart you are. (I'd use a different term on the other side of the hyphen, but that would get me in trouble!)

As far as I know, Filemaker isn’t a toy but a productivity tool. Its behavior is at work since many years and Apple (which own FileMaker) never introduced a switch allowing users to disable Autosave.

Apple staff, not only engineers,  thought during months to define how they will embed Lion’s features in their apps. They clearly said that iOS and OSX will be more and more close.

So, how may you seriously dream that they will introduce such a switch in their new apps?

I may be wrong but, since my first message in this thread I try to explain that the machine is blindly running exactly as the tanks in Prague or in place Tien An Men. It will just drop users which don’t accept the changes.

Apple staff is accustomed to drop old users which disagree with changes. Be sure that they will not cry if you leave the boat.

In French we have a good old formula : "Un de perdu, dix de retrouvé" ("One of lost, ten of found").

With or without you, for the best of for the worst, the changes will go on.

Yvan KOENIG (VALLAURIS, France) dimanche 30 octobre 2011 20:12:13

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

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community

What on earth is your problem, Yvan?  How many times are you going to find it necessary to post the same stuff about your preference?

It would be better if you took more time to think through your posts instead of blindly disagreeing with everyone who writes something that you take exception to.

We have our opinions/preferences and you have yours.  Why can't you just accept that and move on?