When an unconfirmed face is rejected it should tagged as unknown and keep the face area. But if one rejects a suggestion the face area is deleted.
And how should an invalid face area be deleted, if not by rejection? I see no mistake here, either give it a name or leave it as unknown. If it was unintentionally rejected, it is now also possible to search an album or a single image again for faces. Maik
After 3 weeks of work, i finally completed the compilation of AppImage using Qt 5.11.3 + QWebkit 5.212. New 6.1.0 pre-release AppImage bundle can be found here (64 bits only for the moment) : https://files.kde.org/digikam/ Please check if this bugzilla entry still valid. Thanks in advance Gilles Caulier
I just noticed that bug too. It's still present in the last appimage (digikam-6.2.0-git-20190618T151249-qtwebkit-x86-64.appimage). If a suggestion from the "Unconfirmed" list is rejected, it means that that face does not belong to the person digikam thought it was. But it is still a face, so it should not be deleted altogether. When rejecting a confirmation, the face should either return to the "Unknown" list, or try and suggest another name. (also, currently "Unconfirmed/Suggested" faces appear in two places in the Personal panel: within the "Unconfirmed" list, and within each suggested person's. Maybe just the latter would be enough?)
The function was / is meant to reject things that were wrongly recognized as a face. For example, a car tire that has been recognized like a face must be able to be removed. It is not meant to reject a wrong suggestion. You can correct or ignore the suggestion. Maik
Ok, but then it is misleading. Basically you have a text box showing you a name and asking whether it is right or wrong with big green and red buttons. Most people will assume that these buttons are meant to confirm if that face corresponds to that name, not whether that is a face or not. Specially when these two buttons and the name appear at the same time when the user clicks on that face. Moreover, there is a X sign at the top right corner of each face that does exactly that, remove the face from the image, so the red "minus sign" button would be redundant.
Created attachment 121195 [details] Redundant buttons when face tagging?
Of course we can assign different behavior to the two buttons. The round X removes the face, the minus button rejects the suggestion and assigns the item unknown again. At the moment I can not change it, we have a student who works on improving the face workflow. To prevent problems later merging the code, I have to avoid making changes to parts of the code where the student works. Maik
Maik, Just CC with bugzilla Igor about this entry. Like this he will add this file to the list of tasks to do while the Face Workflow improvement project... Gilles
7.0.0-beta1 is out with new Face Recognition algorithm based on Deep Learning/Neural Network API from OpenCV https://download.kde.org/unstable/digikam/ Please test and give us a feedback Thanks in advance Gilles Caulier
On a somewhat related issue, whenever we delete a tag from a confirmed face. For eg. If I had confirmed a suggestion, but later realized it is incorrect. I will do a Remove Tag -> People/Kartik. I think this should return the image back to unknown, however it rejects the image as a face. We will have to scan it again, to get it back to unknown.
*** Bug 419047 has been marked as a duplicate of this bug. ***
Gilles, this bug report may be closed now. I have implemented functionality, to reject Faces if the Red Minus Button is pressed. Kartik
❤️