OS X Lion "feature"

red1

Well-known member
UKGSer Subscriber
Joined
Nov 5, 2007
Messages
2,016
Reaction score
2
Location
Lincs, England
When I upgraded from Snow Leopard to Lion one of the things that pee'd me off was the loss of " Save as" from Preview as I used it for general image cropping/resizing etc.
Still not fully aware of the "Save version", etc., etc., that replaced it.

I've now come across another "funny" thing with Preview. Scenario as follows:

Open image in Preview.
Drag mouse across image to select a section of image.
Ctrl K to crop
Click red Button to close window.

AFAICR a window would open asking if you want to save ( as in Windows ) but not Lion. The amended image is automatically saved back to the original folder.

Can you stop this happening as I've messed up a few images.


Sent from my iPad using Tapatalk HD
 
I've just had a look at this. In Preview, instead of Save, try Export, it seems to give the same options as Save as used to give.

For safety's sake, I'd make a copy, then crop that one. It is bizarre. I'm sure it's all part of a bigger plan, but I've been using Macs since 1990 and I haven't yet fathomed out the versions thing.
 
I sometimes think Apple are losing the plot. They seem to just change things to be different. What was wrong with "save as"? Everyone knew how it worked, how to use it, so why change it?
I'll try your export method.
Cheers


Sent from my iPad using Tapatalk HD
 
Or try going to the File menu and select "Duplicate".
Then select "Save . . ."

Seems to do the same as "Save As" for me but takes longer. I'm not a fan of the autosave thing having spent years deciding when I want to save !

Paul
 
Doesn't iPhoto in Snow Leopard do something similar.

However if you look in the actual file system iPhoto keeps a copy of your original image plus images for any mods you might. Meaning you can roll back within iPhoto or dig around in the file system to find the original. Maybe Lion is doing the same thing.

Mind you I did not like iPhoto either because of that, so stopped using it.
 
I sometimes think Apple are losing the plot. They seem to just change things to be different. What was wrong with "save as"? Everyone knew how it worked, how to use it, so why change it?

I am a great fan of Apple Hardware and Software but certainly agree with your comments about changing the "Save As" way of doing things. I find it quite annoying. It was like when Microsoft Office products started shortening their displayed menus and it then took you more mouse clicks just to carry out simple tasks. If it's not broke just leave the bloody thing alone :mad:
 
Just found this on a blog:

........................

The autosave feature in OS X 10.7 has been a mixed bag. It's nice that it saves things for you, but it's not nice that automatically saves things that you don't want to change permanently, or that the "Save As..." option has disappeared. The good folks at stack exchange have discovered a remedy.

To disable autosave in TextEdit.app, run the following command in Terminal:
defaults write com.apple.TextEdit ApplePersistence -bool no
This disables autosave and versions, reenables the "Save As" option and hot-key (Command-Shift S), and reenables Command-D as a hot key for "Don't Save".

For TextEdit, you'll run into sandbox-related permissions errors with this with the old style Autosave, where it attempts to place a file name "filename (Autosaved).txt" in your working directory. I don't know a good fix for that (if someone does, would you mind making a comment?)

This works for other apps as well, just replace TextEdit with the name of the app, e.g.:
defaults write com.apple.iWork.Keynote ApplePersistence -bool no
defaults write com.apple.Preview ApplePersistence -bool no
It is such a relief to have that "Save As..." option back! Hopefully I'll be able to get something done in Lion now with a minimum of cursing.

[kirkmc adds: We know that Save As is coming back in Mountain Lion, but if you want to turn of autosave for a specific application, this is good to know.

I'm not sure about these sandboxing errors. After working with a TextEdit file for a bit, I got an error saying, "You don't have permission to write to the folder that the file "test" is in." To be honest, that kind of outweighs the usefulness of turning off autosave; so if someone can find a solution for that, I'd say this hint might be more useful.]
...............

Like the bit about "save-as" coming back with Mountain Lion!!!!


Sent from my iPad using Tapatalk HD
 


Back
Top Bottom