P: Exclude some sliders from Previous button

While trying to reproduce the problem, I found out that I had a different idea of what "Previous" means compared to the implementation.

I understood it to refer to "previous edits", however it means "edits of previously selected image".

With my earlier understanding I expected to be able to do the following:
1. Make edits to image "A".
2. Use the cursor keys to move to another image "C", visiting image "B" on the way.
3. Press "Previous" and thus copy the edits I performed on image "A" to image "C".

This didn't work as I expected since the intermediate visit to image "B" causes the "Previous" reference to be directed to "B" rather than "A".

Because in my scenarios image "B" almost always has no edits at all, pressing "Previous" for image "C" seemed to have no effect at all.

Now that I understand that "Previous" refers to "edits of the previously selected image" rather than "edits of the previously edited image", I can make better use of the button.

Not entirely sure which of the two behaviors (my earlier expectation vs the actual) is more intuitive / makes more sense.

While trying to reproduce the problem, I found out that I had a different idea of what "Previous" means compared to the implementation.

I understood it to refer to "previous edits", however it means "edits of previously selected image".

With my earlier understanding I expected to be able to do the following:
1. Make edits to image "A".
2. Use the cursor keys to move to another image "C", visiting image "B" on the way.
3. Press "Previous" and thus copy the edits I performed on image "A" to image "C".

This didn't work as I expected since the intermediate visit to image "B" causes the "Previous" reference to be directed to "B" rather than "A".

Because in my scenarios image "B" almost always has no edits at all, pressing "Previous" for image "C" seemed to have no effect at all.

Now that I understand that "Previous" refers to "edits of the previously selected image" rather than "edits of the previously edited image", I can make better use of the button.

Not entirely sure which of the two behaviors (my earlier expectation vs the actual) is more intuitive / makes more sense.

I use it constantly and I've never seen it fail, so if you can narrow down some reproducible steps it'd be worth repeating.

I use it constantly and I've never seen it fail, so if you can narrow down some reproducible steps it'd be worth repeating.

Very good idea. Adjustment brush strokes are rarely transferable across images either (maybe the suggested "move brush stroke sets"-FR would help).

I'm not sure whether it is worth creating a bug report for this but does anyone else have the problem that the "Previous" button often fails to work? Just moving between some images seems to inactivate it many times, while I'd still be able to reuse the last set of image edits I created.

Without talking about how to implement it, I would also love to see some selection of corrections applied by "Previous". I'll leave the implementation to the GUI specialists ....

Beat

I can see the merits for red eye and spots but implementation ......mmmmmmm

Agreed, I wouldn't want it popping up the dialog each time either. Considering Alt-clicking works all over the place, I'd consider doing an Alt-click to show the dialog, and then it'd be a set it and forget it dialog most of them time. Perhaps change the button text to 'selective previous' when not all checkboxes are checked, just as a visual reminder.

I think there would need to be some simple way to have it work instantly as it does now without the sync dialog popping up, and only have the dialog pop up when you want it do. I'm not that fond of "hidden" features like holding down a modifier during a click or something (LR has tons of these) unless there's some text somewhere indicating such a feature is available when you are using it without the modifier. So I'm not sure of the UI but I do support the idea in general.