| Summary: | 'Auto toggle parents' unnatural behavior when removing a tag | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Sebas <djsebas> |
| Component: | Tags-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | minor | CC: | caulier.gilles, imolb |
| Priority: | NOR | ||
| Version First Reported In: | 8.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Sebas
2017-10-06 16:58:21 UTC
digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier This still applies. It is unnatural. I backup Sebas concerns. The setting of tags works pretty fine.
But the removing is not intuitive.
Let's take the following example to illustrate:
[ ] Grandparent
[ ] Parent1
[ ] Child1
[ ] Child2
[ ] Parent2
[ ] Child3
[ ] Child4
The "toggle auto" setting is set to "parent".
I select Child1 and Child3. Result (with digikam 7.2.0):
[X] Grandparent
[X] Parent1
[X] Child1
[ ] Child2
[X] Parent2
[X] Child3
[ ] Child4
So far fine.
Now I realize Child3 was a mistake and I deselect it. What happens:
[ ] Grandparent
[X] Parent1
[X] Child1
[ ] Child2
[ ] Parent2
[ ] Child3
[ ] Child4
Now Parent1 is active without the Grandparent being active.
What I would expect (maybe as optional feature):
[X] Grandparent
[X] Parent1
[X] Child1
[ ] Child2
[ ] Parent2
[ ] Child3
[ ] Child4
So I would change Sebas rule
* When removing a tag, remove that tag and its children.
to
* When removing a tag, remove that tag and its children and its parents if these have no other child elements active.
@sebas, digiKam 8.0.0 is out. This entry still valid with this release ? Best regards Gilles Caulier (In reply to caulier.gilles from comment #4) > @sebas, > > digiKam 8.0.0 is out. This entry still valid with this release ? > > Best regards > > Gilles Caulier Hey, Yes this still applies. Hi, The 8.7.0 pre-release Windows installer from today have been rebuilt from scratch with Qt 6.8.3, KDE 6.12, OpenCV 4.11 + CUDA support, Exiv2 0.28.5, ExifTool 13.27, ffmpeg 7, all image codecs updated to last version (jxl, avif, heif, aom, etc.). Please try with this version to see if your problem still reproducible... https://files.kde.org/digikam/ Thanks in advance Best regards Gilles Caulier Problem still exists with digiKam-8.7.0-20250411T180056-Qt6-x86-64.appimage |