Lightroom: image-specific undo (c-alt-z)

  • 8
  • Idea
  • Updated 7 years ago
Global undo is frequently counter intuitive, unexpectedly bouncing me info a different module or different image. Undoing a module change just isn't something I consider history to be undone.

Add an image-local undo to wind back through the edit stack - preferably bound to c-alt-z so that it's consistent with PS.
Photo of Barrie Spence

Barrie Spence

  • 14 Posts
  • 0 Reply Likes
  • driven daft by the global undo - that and the fact that I come out of PS and c-a-z doesn't do anything

Posted 7 years ago

  • 8
Photo of john beardsworth

john beardsworth

  • 1041 Posts
  • 239 Reply Likes
You have the history panel for going back through individual edits. But I agree a module change isn't necessary to undo.

Ctrl Z is the right choice. Lightroom shouldn't be replicating Photoshop's inconsistencies with other Windows programs.
Photo of Beat Gossweiler

Beat Gossweiler

  • 238 Posts
  • 38 Reply Likes
I think for certain "undos", a module change is necessary to see the effects as they were before (i.e. undo-ing a stack).
Photo of Sean Phillips

Sean Phillips

  • 159 Posts
  • 44 Reply Likes
I use the global undo, including module change, all the time an I would be lost without it. It is an essential feature. Taking that away would change my entire workflow.
Photo of john beardsworth

john beardsworth

  • 1041 Posts
  • 239 Reply Likes
Do you find the module undo useful? I don't find it a problem, but am surprised anyone likes it.
Photo of Mark Sirota

Mark Sirota

  • 146 Posts
  • 29 Reply Likes
I do find it helpful. In the unusual case that I'm undoing a whole set of changes (usually because I was just testing something), when I get back into Library I know I've undone everything. I could, of course, use snapshots for this instead.
Photo of Sean Phillips

Sean Phillips

  • 159 Posts
  • 44 Reply Likes
Yes, I do find it useful. Mark described one perfect situation. Extending that even further... I use Auto Sync all the time. I generally select a few images at a time that I can apply some global edits to (or even some local edits for very similar images). I often find myself flipping between Loupe, Grid, and Develop during this process. If I need to undo something from several steps ago then it can be really helpful to actually see the module change to know exactly where in the process I am.

Note also that selecting a different history state does not apply to multiple images, so without global undo you would have to do this for every individual image.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Regardless of the rationale for module changes as undo, if you know that what you want to do is back out develop adjustments to a single photo, then the edit-history could hardly be more appropriate.

Summary:
------------
I agree that what gets undone when invoking "Undo" is often a "discover-as-you-go" proposition, however there is already a far better way of undoing individual image edits - the beloved edit-history list.
Photo of Scott Mahn

Scott Mahn

  • 178 Posts
  • 45 Reply Likes
I just don't like not knowing what the next undo will do.

Is it possible to have a global history path so we know where the next CMD Z will put us?
Photo of Mark Sirota

Mark Sirota

  • 146 Posts
  • 29 Reply Likes
You can always redo it (shift-command-Z) if you don't like it. Anything that can be undone can be redone. Seems a lot more efficient than going elsewhere to view the undo stack.
Photo of Sean Phillips

Sean Phillips

  • 159 Posts
  • 44 Reply Likes
Or ctrl-Y. I totally agree with Mark.
Photo of Scott Mahn

Scott Mahn

  • 178 Posts
  • 45 Reply Likes
God bless you guys if you never get lost in your undo's and undoings of undo's. I know I do.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
my .02: most of the time module change undo is a bother, but I sure would not want it removed for times that it is helpful. Using keyboard modifier or something to create a "undo sans module changes" might be nice. Also, the title for undo items is programmer's choice - consider an FR for more descriptive Undo titles, maybe even an option for tooltip to go with it.

"Undo Module Change from Library to Develop" - not sure what a tool tip for this would be, or:

"Undo Module Change" - tooltip: "from Library to Develop..."

Likewise, if there are other Undo operations that leave you guessing, consider a better title...

PS - Plugin operations share the undo stack - Note to self: remember to use good undo titles.
Photo of TK

TK

  • 531 Posts
  • 110 Reply Likes
I think there is a case to be made for both "global undo" (the current implementation) and "image-specific" undo.

Perhaps the latter wouldn't be missed as much, if one had access to an essential history that only shows effective edit actions. The latter could be chronologically ordered (current implementation) or, alternatively, allow a logical grouping of edit actions.

In either view, it should be possible to undo any step, not just the last one. However, I agree that a keyboard shortcut to undo the last image editing step (which might have been done days ago, but one wants to undo it when one visits the image) would by useful.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I agree: presently, "edit history" covers the need for image-specific undo, functionally. And, it would be easy enough to implement a keystroke that backs up one step in the edit-history stack, effectively implementing image-specific undo. But, I can't help but want the even more powerful changes to edit-history that TK has suggested.
Photo of Geoff Walker

Geoff Walker, Champion

  • 214 Posts
  • 43 Reply Likes
Yes a screen prompt of what is being undone when crtl-z is used would be, hopefully easy to implement and satisfy the request.
Photo of TK

TK

  • 531 Posts
  • 110 Reply Likes
Geoff, by "screen prompt" do you mean a dialog box that asks whether one wants a global or local undo? I'd find that unacceptably slow / cumbersome. I think two different keyboard shortcuts are warranted for these two different functionalities.

If you meant "visual feedback" then I don't think that it satisfies the request because the OP wants to be able to specifically target a local image-edit undo, rather than just seeing what kind of undo (global vs local) is performed.

BTW, some of us would love to have an option to move visual feedback off the central image area.
Photo of Geoff Walker

Geoff Walker, Champion

  • 214 Posts
  • 43 Reply Likes
Sure two keyboard shortcuts would be great, I just made a suggestion which has validity the same as the OP's.
Photo of Mel Brown

Mel Brown

  • 5 Posts
  • 0 Reply Likes
(LR3.4.1) This is not a bug, but what I see as a design error.

Example: In the Develop module, I adjust Image01. Then I select Image02 and make an adjustment to it. Then I return to Image01 and make a second adjustment to it. Then maybe I decide I don't like either adjustment to Image01, so I press Ctrl-Z twice, intending to remove the two adjustments I made to Image01. Unfortunately, that undoes the second adjustment to Image01 and the one adjustment to Image02, which I did not want to undo.

Sure, the undo is faithfully retracing my steps, but that makes no sense to me. I would prefer that the undo stick with the currently selected image. If for some reason some people like it the way it is, then please, at least give me an option in Preferences to do it my way.

This reply was created from a merged topic originally titled
Lightroom: Undo (Ctrl-Z) should limit its actions to the currently selected image..