If a User deletes a Face Region (using the Rejection Overlay cross button), then the Face shouldn't remain marked as "Scanned". The user should be easily able to recover the image using the "Face Scan -> Skip Images Already Scanned". Instead to recover it, the User will have to "Scan all and Merge Results", which is time consuming. Here's a video about what I mean : https://imgur.com/a/p0W0yfl When I try to run "Skip Scanned Images", the Algorithm thinks that all images have been scanned already. I feel this is because the deletion of Face Region, is not un-marking the Face as "Scanned". Please check if this bug is reproducible, in case it's just a problem with my branch. Kartik
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.