LIGHTROOM: Automatic advance behavior

  • 2
  • Problem
  • Updated 6 years ago
  • (Edited)
When "automatic advance" option is active in gallery module, whatever you change in flags, stars or picked/rejected... Lr automatically moves to the next photo.

At this point everything is OK. But, in LR 4.4RC at least, if you have selected for example the 20th photo and you change a flags or classification of another photo (not selecting this other) Lr automatically moves the selected photo to the 21th.

I think, IMO, that this automatic advance should be when you make a change in the current photo.

It's a small behavior but better one.
Photo of ImanolZ

ImanolZ

  • 71 Posts
  • 5 Reply Likes

Posted 6 years ago

  • 2
Photo of Rikk Flohr

Rikk Flohr, Champion

  • 1373 Posts
  • 335 Reply Likes
It sounds like you might have changed your sort from User Order (or whatever it was set to) to Edit Time A-Z
Photo of LRuserXY

LRuserXY

  • 426 Posts
  • 41 Reply Likes
I can reproduce it on LR 4.3 (Win 7 64 Bit) with normal "sort: file name" and using the context menu (I think that was the point).

To reproduce e.g. in grid mode: Select one photo in the middle of the grid so it becomes the target photo, then use the context menu to change e.g. the color label of the first photo in the grid. The result is that the target advances one photo, which is kind of funny.

Auto advance should be ignored when using the context menu, perhaps except for the target photo.

By the way: There is another situation where auto advance does not make sense: When multiple photos are selected and being in grid mode (or in other modes with auto sync enabled): When setting rating/label/flags in this situation, the change is already applied to all selected photos, so it does not make sense to advance the target photo at all.
Photo of Rikk Flohr

Rikk Flohr, Champion

  • 1373 Posts
  • 335 Reply Likes
OK I can duplicate what you are seeing. I didn't catch that you were changing an attribute without selecting the photo That said, I don't believe it would be classified as a bug just an unexpected behavior but probably as designed.