Summary: | wrong number of images in a closed recursive tag | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | noeck <noeck.marburg> |
Component: | Tags-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 0.10.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.0.0 | |
Sentry Crash Report: |
Description
noeck
2009-09-25 21:40:27 UTC
Well it isn't actually a bug, but another way of interpretation :) We could add an option to either display the real amount of images or the recursive amount (although I'm not a fan of adding more and more options to setup, it is already too big). Any other suggestions? Ok, now I see the interpretation you meant. You're right, you can count images or tags (but subsubtags are not counted neither). I use those numbers to check if every picture has a tag of a category, therefore it would be useful. EXAMPLE: (20 pictures are tagged and should have at least one of the following tags, but can have more) - quality (0) '-nice (10) '-important (8) <- e.g. 6 of the nice ones and 2 of the bad ones '-bad (10) gets + quality (28) I would expect + quality (20) then I could easily check if every picture has at least one tag. END OF EXAMPLE I would like the feature, but I think it's up to the developers to decide if adding an option is a good idea. It's not too easy to implement. To get the number "20" in the above example, you must find all subtags for "quality", and make a query for unique image ids tagged with any out of this group of tags. For me the current behavior is enough. No need to make a big puzzle... Gilles I can't estimate the effort that is needed in this case. But according to what Marcel wrote I think it's not worth it. There are so great features already there and to come, so don't waste time on this one. So as I opened this report, I change the status to resolved and I suppose "wontfix" is the right option. |