Bug 430053 - Clarify dialogs when removing unused face tags
Summary: Clarify dialogs when removing unused face tags
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Faces-Workflow (show other bugs)
Version: 7.2.0
Platform: Appimage Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-05 19:48 UTC by Mike Morrison
Modified: 2021-04-04 07:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.3.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Morrison 2020-12-05 19:48:29 UTC
When removing a face tag that is not assigned to any images, some additional info in the dialog popups would help the user to feel more confident about removing them.

In the People view, in the list of tags on the left sidebar, if I right-click on a person's name for which there are 0 assigned photos, and then click "Remove Face Tag", the first dialog asks:
"Remove face tag?"
I would feel more assured if this dialog included the name of the tag to be removed, for example:
"Remove face tag 'Mike'?"

If I click "Yes" on that popup, the next popup asks:
"Remove the tag corresponding to this face tag from the images?"
I find this message somewhat confusing, because there are in fact no images associated with this tag. Perhaps this message, or the previous one, could indicate the exact number of images (0, in this case).

Actually, perhaps both dialogs could be replaced with a single one saying something like:
"Face tag 'Mike' is associated with 0 images. Remove it?"


SOFTWARE/OS VERSIONS
Ubuntu 20.10
digikam-7.2.0-beta2-20201120T061443-x86-64.appimage 
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Comment 1 Maik Qualmann 2020-12-05 20:27:04 UTC
We have discussed these dialogues several times. I have already changed the text to make it clear that only the face tags flag is removed. We will not list all selected tags in the dialog either.

Maik

*** This bug has been marked as a duplicate of bug 429471 ***
Comment 2 caulier.gilles 2021-04-04 07:41:02 UTC
Fixed with #429471