| Summary: | more efficient way of selecting tags | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | songohan2 |
| Component: | Tags-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | caulier.gilles, px79 |
| Priority: | NOR | ||
| Version: | 0.9.2 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.5.0 | |
In general I like the idea... right now you can also achieve this by creating a search for that: advanced search->Tag->equals->animal (but I guess this only works correct in the upcoming 0.9.4 release, I had to patch some query settings in the advanced search dialog some time ago). yes, but that would not be very intuitive.. i'm suggesting to simplify these things.. the whole tag-thing is not very intuitive as long as (see above) the sum of all sub-categories does not equal their parent.. this is called anomaly in data analysis.. imagine this with files.. like in the windows explorer, if there was a flat view on the right (recursive). I think this bug is fixed now: I don't know, when this features was introduced exactly, but in digikam you can toggle from the main-menu: "View" -> "Include Tag Subtree" This way, you can enable/disable automatic-child-selection. You can even assign a keyboard shortcut to this switch: "Settings" -> "Configure Shortcuts" I forgot the version number, sorry. I found this option in digikam 2.3.0. |
Version: (using KDE 3.5.9) How to get rid of the "Include tag subtree" toggle. This approach is standard in OLAP-Applications. I think it can lead to a usability jump in digikam/tag-hierarchy. The tag-filter-bar on the left shows the following: animal |- dog |- cat All parent-tags apply to children automatically (its a ordinary hierachy!?!). These are my applied tags: - pictures of my dog => animal/dog - ... of my cat => animal/cat - ... some animals yet to identify => animal The Problem: How to select tags including or not including children ? Solution: Introduce a virtual child-node that represents its <parent-tag without children>. animal <---- selects animal with children ("all animals") |- <other> <---- selects animal without children ("unspecified animals") |- cat <---- only animal/cat |- dog <---- only animal/dog This simplifies our view of the hierarchy: The sum of all children leads to the same set of pictures as their parent. The virtual child makes sure we don't miss pictures that are not (yet?) assigned to a real child-tag. Now we don't have to toggle anything. Thats it.. Questions? What do you think?