[Digikam-devel] [digikam] [Bug 303690] hierarchical tags inconsistencies

[Niels]

https://bugs.kde.org/show_bug.cgi?id=303690

Niels <niels.misc at noyo.dk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |niels.misc at noyo.dk

--- Comment #2 from Niels <niels.misc at noyo.dk> ---
My problem with this is that the hierarchical tag system in Digikam simply
doesn't work as I would expect. I'm not saying it's wrong, just unexpected.

>From the term "hierarchical", I would expect that selecting a child tag always
selects all parents. Maria is always people. Norway is always Europe.
Butterflies are animals.

Suppose I have the following structure for a given image:

[ ] Cities
--- [ ] Amsterdam
--- [ ] Hamburg
--- [x] Trier

[x] Routes
--- [x] Long
--- [ ] Short

In Album View, this is then shown under the image: "Routes, Long, Trier".
If I enable "Short", it becomes "Routes, Long, Short, Trier".
I don't see how that system is convenient.
Also, the order in which I enable tags matter, so that related tags can end up
not being next to each other in this comma-separated list.

The tool tip for the first case shows:
Routes
Routes/Long
Cities/Trier

Here's what I would expect:
1) That Cities was mandatory.
2) That Album View and tool tip showed something like "Cities/Trier,
Routes/Long, Routes/Short".

The fact that parents aren't mandatory is, imho, your imposed interpretation of
how a hierarchy should work. It would probably be good to separate the issues:
1) Should parents be mandatory? How should a tree structure of tags work?
2) How should tags be shown? Full list, compact list, single tag nodes or
concatenated?


Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.