| Summary: | Deleted Faces don't re-appear in Face Scan with "Skip Images already Scanned" | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Kartik <kartikx2000> |
| Component: | Faces-Workflow | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin, pedja |
| Priority: | NOR | ||
| Version First Reported In: | 7.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.2.0 | |
| Sentry Crash Report: | |||
|
Description
Kartik
2020-06-17 16:10:15 UTC
But a face that I delete should never be found again. The fact that we need a way to get it back is another matter. Again, how users imagine it and how you should implement it: Let's say the automatic face detection finds a car tire as a face. With a click on the overlay button (x) this car tire is removed. It no longer appears on the image as a face marker and a re-scan will not suggest it as a unknown face again. The face recognition suggests a name for a face, with a click on the (-) button the suggestion is rejected and the image appears again under unknown. Maik (In reply to Maik Qualmann from comment #1) > But a face that I delete should never be found again. The fact that we need > a way to get it back is another matter. Again, how users imagine it and how > you should implement it: > > Let's say the automatic face detection finds a car tire as a face. > With a click on the overlay button (x) this car tire is removed. It no > longer appears on the image as a face marker and a re-scan will not suggest > it as a unknown face again. > The face recognition suggests a name for a face, with a click on the (-) > button the suggestion is rejected and the image appears again under unknown. > > Maik Understood. I was considering the (x) button to function as a "Reset this Face", when that is not the intention. Kartik *** Bug 423387 has been marked as a duplicate of this bug. *** Gilles, this bug may be closed. This feature is not needed. |