Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Closing/colapsing an image stack causes another stack to open/expand

Engaged ,
Oct 31, 2017 Oct 31, 2017

I'm using Photoshop Elements 15 Organizer.  I have a folder with a large number of image stacks.  Each stack is an exposure bracket sequence.  If I open one of the stacks to view a thumbnail of all the images in the stack, they are displayed as they should be.  When I click on the little close/colapse icon on the last image, the stack colapses, but another stack is opened/expanded.  The stack that is opened is usually, but not always, the stack two locations further along in the stack sequence.

I've also noticed that if I've double clicked on the thumbnail for an image in an opened stack it will display full screen as I'd expect.  But then if I scroll to last image of the stack and click on the close/colapse icon, it will close/colapse the full screen stack, but when I go back to the thumbnail view the stack is still expanded.

What's going on?

419
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Expert , Nov 01, 2017 Nov 01, 2017

I can reproduce that (annoying) stack behaviour.

My workaround is to right click, select version set and 'collapse items in version sets'.

Translate
Community Expert ,
Nov 01, 2017 Nov 01, 2017

I can reproduce that (annoying) stack behaviour.

My workaround is to right click, select version set and 'collapse items in version sets'.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Nov 01, 2017 Nov 01, 2017
LATEST

Michael,

On the one hand I’m glad you can reproduce the issues, on the other hand it raises a red flag about the thoroughness of testing on this release. Makes me wonder how the defect could have been missed. Maybe the test suite is deficient. Fortunately, this is a problem whose impact is confined to the “high user irritation” category. Does Adobe log this defect so that it is considered for correction in a subsequent release?

Bill

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines