https://bugs.kde.org/show_bug.cgi?id=490793
--- Comment #3 from Roland <carbonwer...@hotmail.com> --- Hi Maik. Im not sure I understand the change here. Is the idea that if n=1, it will have 'reference image' superimposed? If so, I would suggest this is probably going to be confusing. That is, a > 0 row return on a query means there is a match to the query. And that is how we think about the concept of 'similar' in the real world. If I walk into a clothing store and ask if there are any pants in the store that look similar to mine, the clerk is never going to point at my pants as the response. If we get a positive response, the implication is that there are other matches, not including the reference, in the return. And the concern with this in the context of Digikam- especially with a multi-user instance, or with aggregations of content- a hit may mean to the user that the image is already cataloged OTHER than the source file. They then delete the similar item vs categorizing it, and now the system has 0 instances of the file. Wouldnt it make more sense to simply exclude a return if the search engine returns the same file name AND the same path? It seems far more useful and consistent to be if a find similar call returns 0 if the number of items isnt > 1. Its the same as deduplication; we dont want to see a hit on items without matches that are within the degree of similitude defined. -- You are receiving this mail because: You are watching all bug changes.
