Locking development

[ron_c]

Is there any way to lock the settings of an image in the development module, so that no further changes can be made. I need to protect my "perfectly prosessed" images from my constant tinkering : .

Ron

 

[Brad Snyder]

Not per se.

You could create a snapshot at the point of 'perfection', which would remain with the image, so that you could always return to it, regardess of future 'abominations'. Returning to the appropriate history state would work as well.

 

[Winston]

I make a snapshot. It doesn't lock anything but you can get back to it with one mouse-click.

 

[clee01l]

[quote author=Brad Snyder link=topic=7431.msg5'669#msg5'669 date=1249229181]
Not per se.

You could create a snapshot at the point of 'perfection', which would remain with the image, so that you could always return to it, regardess of future 'abominations'. Returning to the appropriate history state would work as well.
[/quote]You could also create a Virtual Copy at the point of SnapShot. Tinker all you wish with the VC or the master but not both! I think in this case, a VC would be best because it behaves like a separate image. A named snapshot OTOH, can be written into the XML metadata marking a distinct point of return.

You can give each Snapshot or VC distinctive names like "Perfectly Processed" or Perfection1, Perfection2 etc.

 

[Braders]

[quote author=ron_c link=topic=7431.msg5'667#msg5'667 date=1249228844]
Is there any way to lock the settings of an image in the development module, so that no further changes can be made. I need to protect my "perfectly prosessed" images from my constant tinkering : .

Ron
[/quote]

Then what would be the fun of having LR?!

Make VC after VC and soon you'll see there are more perfect ones hiding round the corner :icon_idea:

 

[ron_c]

Thanks for the info. I will try snapshot

By the way,Cletus, your insect photos look great.

Ron