https://bugs.kde.org/show_bug.cgi?id=481289
--- Comment #9 from mahikeulbody <mcfaro...@gmail.com> --- Ok, that toke me a little time to find these checks because I never used before the Tab panel of Caption sidebar menu (my only tags come from automatic tagging such as face recognition and reverse geocoding). So my misunderstanding of your answers :-( Setting a non-root tree node works as if the higher levels of the tree were set. That does not appear in the Tab panel of Caption sidebar menu but all functions (advanced search, tabs manager, tabs filters, ...) work as if these higher levels were set (AFAIK). So I wonder what benefice there is to write HierarchicalSubject = "A|B|C, A|B, A" over to write simply "A|B|C" except to be able to display A[ ] B[ ] C[x] when in fact that does not reflect that Digikam will work as if we have A[x] B[x] C[x]. If the higher nodes of a node set were automatically set in order be more consistent with the way all functions work in this case (AFAIK again) that would remove the artificial (?) need to write strings as "A|B|C, A|B, A". Also you could take in account that Digikam writes HierarchicalSubject = "A|B|C" when the user drag&drop the tag C onto a photo. In case you would want to "fix" this different behavior between Tab panel of Caption sidebar and drag&drop from Tags filter, my suggestion would be to write HierarchicalSubject as drag&drop does for both Tab panel and Reverse Geocoding. -- You are receiving this mail because: You are watching all bug changes.
