Adobe Community: Message List - Applying keywords to collapsed stacks has changed

Re: Applying keywords to collapsed stacks has changed

forums_noreply@adobe.com — Fri, 28 Dec 2012 21:13:16 GMT

John R. Ellis wrote:

This is cerrtainly the case as far back as Mac version of Lr3.2 but I rcall it dating back even further, but not how far back beyond that.
Interesting -- I searched the forums for various combinations of "stack top keyword tag drag" and saw dozens of messages about keywords only applying to the top of the stack, but didn't find any mentioning the inconsistent behavior of dragging.

I don't believe the inclusion of this specific behaviour was discussed in the public or pre release forums. I suspect very few users, including the majority of pre release testers, were aware of it. It's not documented anywhere that I know of, but I expect that will now change...

John R. Ellis wrote:

Any ideas about the inconsistency? If by design, what's the rationale?

Since the behaviour was never discussed I can only guess as to why the ability to drag and drop keywords works as it does and applying the keywords via the panel doesn't. Anyway, I don't view it as an inconsistency, especially since dragging keywords from the keyword panel on to a thumbnail isn't the most obvious method to begin with. For the majority of users having the ability to auto select on expanding a stack (i.e. double click stack badge or shift+click the badge) then applying the keyword via the panel is a much safer approach.

Re: Applying keywords to collapsed stacks has changed

forums_noreply@adobe.com — Fri, 28 Dec 2012 20:04:03 GMT

This is cerrtainly the case as far back as Mac version of Lr3.2 but I rcall it dating back even further, but not how far back beyond that.

Interesting -- I searched the forums for various combinations of "stack top keyword tag drag" and saw dozens of messages about keywords only applying to the top of the stack, but didn't find any mentioning the inconsistent behavior of dragging.

Any ideas about the inconsistency? If by design, what's the rationale?

Re: Applying keywords to collapsed stacks has changed

forums_noreply@adobe.com — Fri, 28 Dec 2012 18:19:25 GMT

It been the case for some considerible time that dragging a keyword and dropping it onto the image part of the thumbnail will result in the keyword being applied to all photos within the collapsed stack. This is cerrtainly the case as far back as Mac version of Lr3.2 but I rcall it dating back even further, but not how far back beyond that. That being said, I'm fairly sure that the ability to do this went in as part of the Lr3 beta work associated with improving the collapsing/opening of stacks using keyboard modifiers. John B should remember this as we locked horns on exact behaviour.

Re: Applying keywords to collapsed stacks has changed

forums_noreply@adobe.com — Fri, 28 Dec 2012 17:53:04 GMT

In my LR 4.3, if I assign the keyword by dragging it to the thumbnail in grid view, it gets assigned to all photos in the collapsed stack. But if I assign the keyword by typing it in the Keywording pane, it only gets assigned to the top photo.

Re: Applying keywords to collapsed stacks has changed

forums_noreply@adobe.com — Fri, 28 Dec 2012 08:19:41 GMT

Sadly, I can't replicate it. Even if all items are selected before the stack is collapsed, only the top one gets the keyword.

John

Re: Applying keywords to collapsed stacks has changed

forums_noreply@adobe.com — Fri, 28 Dec 2012 03:44:05 GMT

good news, i think

vince

Applying keywords to collapsed stacks has changed

forums_noreply@adobe.com — Fri, 28 Dec 2012 03:35:41 GMT

Somewhere between LR 3.4 and LR 4.3, the behavior of applying a keyword to a collapsed stack changed. It used to be that the keyword was applied only to the top photo; now it is applied to all the photos.

This behavior occurs only for adding keywords; if you delete keywords or change flag, label, date, caption, etc. it only applies to the top photo in the stack.

Did I miss a feature announcement in the release notes?

http://forums.adobe.com/message/3853365#3853365