 |
 |
I'm pretty sure I hate the auto-save feature...
|
|
|
|
|
Senior User
Join Date: Jan 2006
Location: Naugatuck, CT
Status:
Offline
|
|
anyone figure out a good way to disable it??
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Nov 1999
Location: 888500128, C3, 2nd soft.
Status:
Offline
|
|
It's exactly the same thing as it was before, except you have to save a Duplicate FIRST when you branch off the first new version, and never worry about losing anything.
After that, the process is exactly the same as it's always been:
Major change: Save new (Duplicate) to Project 1.1. Save/Auto-save as you make changes, next major milestone: Save new/Duplicate to Project 1.2.
At least, that's how I've been working for years.
|
|
|
| |
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2004
Location: FFM
Status:
Offline
|
|
The only problem with auto save is unintended changes.
|
|
|
| |
|
|
|
|
|
|
|
Posting Junkie
Join Date: Dec 2000
Status:
Offline
|
|
Unfortunately, that's a pretty big problem.
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Nov 1999
Location: 888500128, C3, 2nd soft.
Status:
Offline
|
|
That's what Versions is for.
|
|
|
| |
|
|
|
|
|
|
|
Posting Junkie
Join Date: Dec 2000
Status:
Offline
|
|
Until you get reason to believe that you might have made an accidental change somewhere along the line to a rather large and not very skimmable file, and the only way to find out is to successively revert to each version and then make a duplicate of the file, so that you can diff them by hand with FileMerge to see what changed each time.
This happened to me just the other day...
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Nov 1999
Location: 888500128, C3, 2nd soft.
Status:
Offline
|
|
Isn't that still preferable to not having a saved version of that state at all?
|
|
|
| |
|
|
|
|
|
|
|
Posting Junkie
Join Date: Dec 2000
Status:
Offline
|
|
Under Snow Leopard, there wouldn't have been any need for it. The accidental change (when I only meant to view the file) would have triggered a warning upon closing the document, at which point I would have clicked "Don't Save" and that would have been the end of it.
The same thing could be implemented on Lion if there was an option to enable a "This document has changed since you saved it. Was that on purpose?" dialog that would revert the change if you clicked "No", but nothing like that is implemented, and as it currently stands, the system is prone to accidental changes.
|
|
|
| |
|
|
|
|
|
|
|
Clinically Insane
Join Date: Nov 1999
Location: 888500128, C3, 2nd soft.
Status:
Offline
|
|
Ah—that makes sense.
Logic still gives me that prompt under Lion, so I hadn't noticed its by-default absence.
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top