Bug 196925

Summary: "Tags aleady assigned" does not show tags already assigned
Product: [Applications] digikam Reporter: DGardner <damien>
Component: Tags-EngineAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, gandalflechner
Priority: NOR    
Version: 0.10.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 7.6.0
Sentry Crash Report:

Description DGardner 2009-06-17 21:56:11 UTC
Version:           0.10.0 (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

If I click on the "Tags already assigned" button near the bottom
of the "Caption/Tags" panel, the tag tree is filtered according to
the tags set on the current image, but the tree is not expanded to
show the actual selected tags if they are not already visible.

For example, I have an image of the Auckland skyline and the tag
assigned is "Places/New Zealand/North Island/Auckland". None of
the the parent tags in that sequence are assigned, just the one at
the deepest level. If the tag tree is collapsed and only showing
tags at the "Places" level, then clicking on "Tags already assigned"
just shows me the unexpanded "Places" tag and I have to expand all
of the levels manually to find out what specific descendant tag is
selected. If the tree is completely collapsed to just the "My Tags"
root tag, then clicking on the "Tags already assigned" button has
no visible effect until the tree is expanded manually.

Can this be changed to expand the tree as necessary to ensure that
all of the assigned tags become visible when "Tags already assigned"
is clicked?
Comment 1 caulier.gilles 2009-06-18 10:34:56 UTC
I cannot confirm this with current implementation from svn...
Gilles Caulier
Comment 2 caulier.gilles 2009-06-21 18:32:35 UTC
*** Bug 197399 has been marked as a duplicate of this bug. ***
Comment 3 Andi Clemens 2009-10-25 02:02:53 UTC

*** This bug has been marked as a duplicate of bug 197399 ***
Comment 4 DGardner 2009-12-09 21:09:05 UTC
Seems to work fine now in 1.0.0-rc1
Comment 5 caulier.gilles 2022-01-22 17:26:16 UTC
Fixed with https://bugs.kde.org/show_bug.cgi?id=197399