Want to resave a document monthly in order to make small change each month but save the previous ones (monthly billing). Is there any way? If not, will Apple issue me a refund so that I can buy Microsoft again? This is a huge billing problem for me!
iMac, Mac OS X (10.7.3)
Hold down the option key as you select Save in the File menu, or command shift s
This will make a duplicate of the file as it currently is.
If you have already made changes to the file but don't want them in the original, select the original file and go:
Menu > File > Revert to > Last Saved
Apple changed this when it set up Auto-Save by default.
IMHO it is very bad User Interface as it is concealed, and expects Users to behave in anticipation which is always bad practice. People do not work that way, they do what is on their mind then save. Further Apple's tiny percentage of users have to learn to behave differently than everyone else and adapt their behaviour according to not just whether they are on MacOS but according to what version of MacOS, subsequently making far more mistakes.
Unfortunately Apple's UI skills and common sense have plummeted on the Mac in recent years, an indication of a change of leadership who seem to want to make their own stamp on the Mac despite they are not quite up to it.
Apple seems determined to kill productivity and whatever work is still being done on Macs, reducing it to a playpen with padded walls, in which they constantly move the furniture for their own amusement.
Peter
Hold down the option key as you select Save in the File menu, or command shift s
This will make a duplicate of the file as it currently is.
If you have already made changes to the file but don't want them in the original, select the original file and go:
Menu > File > Revert to > Last Saved
Apple changed this when it set up Auto-Save by default.
IMHO it is very bad User Interface as it is concealed, and expects Users to behave in anticipation which is always bad practice. People do not work that way, they do what is on their mind then save. Further Apple's tiny percentage of users have to learn to behave differently than everyone else and adapt their behaviour according to not just whether they are on MacOS but according to what version of MacOS, subsequently making far more mistakes.
Unfortunately Apple's UI skills and common sense have plummeted on the Mac in recent years, an indication of a change of leadership who seem to want to make their own stamp on the Mac despite they are not quite up to it.
Apple seems determined to kill productivity and whatever work is still being done on Macs, reducing it to a playpen with padded walls, in which they constantly move the furniture for their own amusement.
Peter
This is another example of Apple trying to get cute and "simplify" the UI but totally confusing everyone. Bring back "save as" and get over the fact that Microsoft has firmly planted that method in the collective conscious of everyone.
Yes, "Duplicate" is basically the same as "save as" -- but it's confusing to have "Duplicate" and "Rename" and "Export" -- all of which have overlapping purposes.
Try this, it works for me, and I am using Mountain Lion.
That's really all there is to it. Nothing to turn on or off, nothing to change in preferences, it works just like before. And you can do this at any time when you are editing the file.
Hi peter
With the new scheme we master the state as we ever did.
-- open a document
as long as we aren't fool enough to embed a living item like a date there is no chjange applied to it.
-- duplicate the document
changes nothing to the original
-- save the duplicate with the wanted name/location so that Autosave will apply
required due to the bug already described
-- edit the duplicate as we want
AutoSave apply
-- close the duplicate document
it saves automatically every changes.
When the described bug will be killed it's during the close process that we will set the name and the location because when it will apply automatically, AutoSave will save in a temporary location (the one displayed in my late screenshot).
One more time, it would be even more efficient if like me you start from templates.
About living dates, when we create a custom one, if we insert a living date in it, it would behave as a really living one in the documents created from the template … only if we don't apply a tip described in the 1st half of 2009. This tip give to this kind of date the same behavior than dates embedded in in-the-box templates. Its value is set to the date of the new doc creation, then it remains fixed.
Every applications accept templates.
Some like : iBooks Author, Keynote, Numbers, Pages require a specific name extension
Others like Preview or TextEdit are ruled by a setting applied in the file's infos window.
Yvan KOENIG (VALLAURIS, France) mercredi 18 avril 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
PeterBreis0807 wrote:
Yvan
A typical example is work that posters send me to determine what is going wrong. Whether I work on the original file or a duplicate, OSX Lion is constantly saving changes I do not want to take effect as I experiment with the file.
I never know at what point the saves are happening without having to examine the file for possibly minute changes. I never know what is the original file, because to open it is to eventually change it.
This applies to many files that I receive as part of my workflow. I do not want to change what the client has given me in any way because it is my reference, my safety net, my legal binding evidence of what was given to me.
If you apply the workflow which I described, the changes apply to the duplicate, no to the original.
When I receive such documents for tests, the first thing which I do is to rename them.
xx.numbers become xx.nmbtemplate
yy.pages become yy.template
zz.key become zz.kth
This way, they behave as template and the original isn't modified.
I'm a bit tired to be forced to repeat this simple scheme so often.
Further I do not want to issue work that has versions in it, because I do not want clients reverting to previous versions and in many cases I do not want them to even see what I may have done.
Trying to keep track of what version of which document has been exported to possibly a further versioned alternate format is a nightmare.
If you choose to trust ranters which don't understand the tool's behavior, no need to ask my advice.
I repeat that versions aren't stored in the documents.
Yes, I wrote once, just after the Lion delivery, that they were stored in the doc but I explained the correct behavior more than twenty times since.
They are stored in a hidden folder which never move to an other device.
On the left I show the folder in which documents are saved.
On the right is the hidden folder whose access is disabled in which datas describing the versions are stored.
I carefully use different verbs.
The system save documents but it store datas describing the versions.
If you duplicate a document from the HD on which it is saved to an other HD, only the document is duplicated.
If you move a document from the HD on which it is saved to an other HD, the datas describing versions are deleted on the original HD.
I described that in detail in :
Versions as a recovery tool
https://discussions.apple.com/thread/3303794
Alas, if I may explain features, I can't read these explanations for you.
I gave scripts able to duplicate the hidden folder in a safe area so that :
(1) we don't loose the datas if we delete a file by mistake
(2) we may replace, for the replicate, the "access denied" status by "read allowed"
This way, if we mistakenly delete a file, or get it corrupted, we may extract (thanks to the two other scripts) the datas related to versions allowing the app to recreate a correct document.
More, when you use the scripts, you see the date when the differents version-datas were stored so you may choose the version to revive.
I'm waiting a bit because I want to try to think to every possible consequences but I plan to file an enhancement request : in the window displaying the versions, replace the doc name which uselessly appear at top of every version by the date-time of these versions. Displaying the doc's name only once at top of the current version seems to be sufficient.
If you think of a possible drawback of such change, let me know.
Of course, I plan also to ask Apple to deliver an official application doing what I offered with my three scripts.
I'm unable to code in C+ so I can't gather the scripts in a single tool whose use would be easier.
Yvan KOENIG (VALLAURIS, France) mercredi 18 avril 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
"Duplicate" then make the changes then "save as..." If you duplicate from Finder then you won't have two documents open on your desktop. The new scheme was so annoying to me that I reverted back to the previous version of iWork to get back "save/save as".
This is how I did it: https://discussions.apple.com/thread/3267033?answerId=15949298022#15949298022 You should be able to find what you need...
Happy hunting
The short answer is "no". You can't turn it off but you can revert to the earlier version of iWork and bypass it. Here is a link describing how to do that:
https://discussions.apple.com/thread/3267033?answerId=15949298022#15949298022
It is a bit of a bother but has worked flawlessly on my old macbook
Well Alan, you seem to be the only one who can answer a simple question with a simple answer. Thank you.
It's a simple matter if you adjust your workflow order to match the new OS.
Each month, before you begin making changes, open your document and File > Duplicate, Command-S..., Command-W. Then continue with the month's edits on the document you opened. You have made and saved an achieve copy of your document as it was when you just opened it and you are in the edit mode for making your monthly additions. It's no more steps than you used before, but it's in a different order.
Jerry
Respectfully beg to differ... Open the doc, make changes, save as... Duplicate and closing the duplicate are extra steps. I know some strongly prefer the new scheme while others of us prefer the former one. I just don't understand why it had to be an either/or approach instead of both/and. Yesterday, I downloaded a little word processing program that allowed me to turn off "autosave" so I suspect that the duplicate/save as... could be "turned off" as well. Obviously, the latest version of iWork retains save/save as on Snow Leopard, so its got to be in there somewhere.
The duplicate and "save as" worked. My version of Pages did not have an actual "Save As" function. Despite the extra step of duplicating, it enables me to do what I want, so that's great. Thank you! What is Command W?
The duplicate and "save as" worked. My version of Pages did not have an actual "Save As" function. Despite the extra step of duplicating, it enables me to do what I want, so that's great. Thank you! What is Command W?
Woffman wrote:
Open the doc, make changes, save as... Duplicate and closing the duplicate are extra steps.
What you describe is not the correct workflow.
Your changes would be store in the original document too and I'm not sure that it's what you want.
The correct workflow would be:
open the doc
duplicate
save the duplicate
edit this duplicate as you want (AutoSave will apply)
close the duplicate when it's ready.
You are free to close the original immediately after duplicating it or keep it open to create new documents.
I use none of these workflows.
I save every document which must be used as starting point to create new ones as templates.
This way I'm sure that the changes which I make can't be stored in my original.
There is a switch in the application.
If the system is Lion it behave the new way, if it's an older system it behave the old way.
Happily, there is no way to change that.
Third party developers are urged to apply the new scheme.
Some refused completely and their app can't enter Mac App Store.
Some deliver the new feature with enable/disable switch. At this time they may enter the M.A.S.
Only those delivering Versions and AutoSave with no enable/disable switch may enter the list of « Lion aware » applications (it's why GraphicConvert was removed from this list).
At this time, Apple applications matching the rule are :
iBooks Author
Keynote
Numbers
Pages
Preview
TextEdit
Guess that others will do when they will be updated.
Yvan KOENIG (VALLAURIS, France) mercredi 18 avril 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
Woffman wrote:
Respectfully beg to differ... Open the doc, make changes, save as... Duplicate and closing the duplicate are extra steps. I know some strongly prefer the new scheme while others of us prefer the former one. I just don't understand why it had to be an either/or approach instead of both/and. Yesterday, I downloaded a little word processing program that allowed me to turn off "autosave" so I suspect that the duplicate/save as... could be "turned off" as well. Obviously, the latest version of iWork retains save/save as on Snow Leopard, so its got to be in there somewhere.
W,
I believe that those arguing that we're discussing a simple on/off switch are missing the point that this change is in harmony with a shift in philosophy, or attitude, or how we think about, the "save" status that Apple is promoting. If we think about our documents as being continuously saved, when we duplicate them we should naturally assume that we are duplicating the current state, not some previous condition. That previous condition is now, more than ever, ambiguous, because it is no longer necessary to ever close an active document and reopen it, or consciously save it, even if we close the application that created it. I predict that at some point when this way of thinking about the save status of documents becomes ingrained we will scratch our heads trying to recall why one would ever assume that "Save As" means to store the document in some previous state.
Jerry
Well said Jerrold.
Glad to see that there is at least one other user understanding the new scheme.
Yvan KOENIG (VALLAURIS, France) mercredi 18 avril 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
how do I do a "save as" on Pages?
