https://bugs.kde.org/show_bug.cgi?id=423113
--- Comment #6 from Minh Nghia Duong <minhnghiaduong...@gmail.com> --- (In reply to Kartik from comment #5) > Hi Nghia, > > The Top Level Connections for the Deleting button are done in > DigikamItemView. The Delete Button forms part of a FaceRejectionOverlay, and > the signal for pressing the delete button is set here: > https://invent.kde.org/graphics/digikam/-/blob/master/core/app/items/views/ > digikamitemview.cpp#L342. > > The > removeFaces(https://invent.kde.org/graphics/digikam/-/blob/master/core/app/ > items/views/digikamitemview.cpp#L411) method then delegates deletion to a > FacePipeline. I think you might be familiar with FacePipeline functionality. > DatabaseWriter works with the FacePipeline and picks up the package (when > its time for being processed arrives), and then calls the FaceUtils method > for actual removal of the Image-Tag association: > > See this connection for DatabaseWriter with FaceUtils: > https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/ > facemanagement/workers/databasewriter.cpp#L142. > > There's multithreaded implementations that lead to DatabaseWriter picking up > the package sent via FacePipeline, however it isn't necessary to worry about > that in my opinion. > > Kartik Thanks, As I see it, FaceUtils only manage face tag and retrieve identity, and FacePipelineFaceTagsIface doesn't hold the information of the registered face embedding. Therefore in order to delete the face embedding in the database, we have to add an additional association between face item and face embedding. If I do it now, it will add up more conflicts to our projects. Therefore I will find a way to do it after the 2 projects merged. Nghia -- You are receiving this mail because: You are watching all bug changes.
