SUMMARY After a face recognition, the recognized people placed in the "Unconfirmed" tag and a counter of new items is supposed to be updated next to each people tag (=number of unconfirmed faces of that people) OBSERVED RESULT After the face recognition is finished, the counter is not immediately updated. It is updated e.g. if you click somewhere in the People left panel. EXPECTED RESULT Counter should be automatically updated when the face recognition is finished. (I don't necessarily expect that it is updated after each individual recognition (could maybe have a negative impact on the performances ?) but at least at the end of the recognition process) SOFTWARE/OS VERSIONS digikam-7.0.0-beta2-20200112T071518-x86-64.appimage
Same similar problem whith: - in Unconfirmed tag, remove reject a face of e.g. "Jack" - The counter associated to "Jack" tag is not updated (unless you click on "Jack"'s tag)
*** This bug has been marked as a duplicate of bug 406586 ***
Fixed with #406586
I reopen this bug: this is not solved in version 7.0.0. In fact there an improvement compared to original bug report (using 7.0.0 beta2): - after face recognition, counter is still not updated. - But there is no need to click somewhere on the left panel to have the counter updated (as before), you just need to move the mouse over the left panel. But as long as you dont move the mouse, counter is not updated.
I definitely cannot reproduce that here, yes there may be a small delay due to performance reasons a timer is running. Which desktop do you use? AppImage? Maik
I just tried, and as Maik i cannot reproduce the dysfunction here, on 2 laptop (Linux and Windows) Gilles
Sorry, my mistake, you are right. But indeed there is a timer (2-3 seconds) before the counter is updated. I made the test by rejecting a face (in "Unconfirmed" tag). I expected that the treatment of rejecting one face would be immediate. That's why I did not realized there was a timer involved and thought the bug was still present. The timer of 2-3 seconds is in this case "too much visible". There are (at least) 2 use cases where the counter must be updated: (1) in case of a recognition process: I suppose you have implemented this timer so that the counter is not updated for each newly recognized face. That can make sense in this case (to avoid negative impact on the performance). (2) in case of a face rejection or assignement (in "Unconfirmed" tag): here the timer is not relevant -> should be avoided So: as an improvement, thanks to check if you can remove the timer for use case (2). Otherwise, you can close this bug.
The timer is necessary, but is only a few milliseconds and is required for many events in a row. In the meantime, writing is also carried out in the face database until the writing in the core database triggers the update. With me here with MySQL there is no visible delay. Writing to the database will be a bit slow for you. I close the bug. Maik