Lightroom: View navigation works incorrectly after creating new collection

  • 1
  • Problem
  • Updated 3 years ago
  • Acknowledged
  • (Edited)
Lightroom 5.7.1

Repro:
- Navigate to Collection A
- Navigate to Collection B
- Select some photos in Collection B
- Create new album with "Include selected photos" (view will switch to new album)
- Navigate backwards (Window -> Go Back, or Cmd-Opt-Left on Mac)

Expected:
- View returns to Collection B

Actual:
- View returns to Collection A

This applies to folders and catalog items in the left bar as well.
Photo of Greg

Greg

  • 9 Posts
  • 0 Reply Likes
  • bleh

Posted 3 years ago

  • 1
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3166 Posts
  • 516 Reply Likes
I can confirm this behavior on Windows. Are you Mac or Windows, Greg?
Photo of Greg

Greg

  • 9 Posts
  • 0 Reply Likes
I'm on Mac, OS X Yosemite.

Thanks for the response!
Photo of John R. Ellis

John R. Ellis, Champion

  • 3382 Posts
  • 854 Reply Likes
Also occurs on my LR 5.7.1 / OS X 10.9.5. As a workaround, you could use the Any Source plugin, which provides backtracking of sources, filter settings, and selections.
Photo of Greg

Greg

  • 9 Posts
  • 0 Reply Likes
Thanks for the tip John.

For anyone else looking for a solution -- John's plugin is pay-what-you-want trialware that does a number of other things in addition to providing a work-around for this bug.

To work around the bug, one could assign a keyboard shortcut to AnySource's "back" command, which will indeed properly navigate backwards to the source collection when creating collections from a selection of photos in one keystroke.

One downside to this approach is that AnySource's back/forward commands are not otherwise direct analogues of the built-in commands, since they only navigate between sources, and not module changes, etc. On the upside, they preserve filters and selections in each navigation state (up to 10 states in history), which patches functionality missing from the built-in commands.

Also, I have managed to get into some inconsistent states using the plugin (so far non-reproducible), so if you are very concerned with stability, take that into account.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3345 Posts
  • 840 Reply Likes
Unfortunately, LR doesn't provide plugins with the ability to read and set the current module.

Even though you can't reproduce the suspected inconsistencies, please send me email (see the Web page) with what you're observing. Thanks!
Photo of Greg

Greg

  • 9 Posts
  • 0 Reply Likes
Too bad about the lack of API access to modules.
Will email with my recollection of the errors I saw.
Photo of Greg

Greg

  • 9 Posts
  • 0 Reply Likes
Thanks for the swift update John!
No issues so far with v1.5.
Photo of Greg

Greg

  • 9 Posts
  • 0 Reply Likes
@Rikk:

I realize this bug is probably not high-priority, but curious if it is likely to be fixed by LR6. As a long-time Photoshop user, I've been disappointed by the big step back in UX that results from the sum of many small issues in LR.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3115 Posts
  • 494 Reply Likes
The bug has been reported.
Photo of Greg

Greg

  • 9 Posts
  • 0 Reply Likes
Thanks Rikk