https://bugs.kde.org/show_bug.cgi?id=320666
--- Comment #32 from Mario Frank <mario.fr...@uni-potsdam.de> --- (In reply to Simon from comment #31) > What I described in Duplicates was wrong. The main image was a grouped > image, so it was hidden (http://i.imgur.com/JKOkJx7.png), but it was > actually there (http://i.imgur.com/2d3OFpM.png). If this is an issue at all, > it is definitely a separate one. > I think using a value of 101 is confusing. If one does not know what it > signifies it looks like a bug. I would just assign a similarity of 100. That > way the main image is still at least in the top group, and when the one > potentially above has a similarity of 100, so is anyway identical. > > The "binary" problem in the image view looks like this: > http://i.imgur.com/r1dhZLq.png > It really is binary, if I use a range below 50% all images have similarity 0 > and a similarity 100 for range above 50%. Hey, the grouped image is something that would be some other issue, I think. Could be something in the imagelister. I changed the similarity of the original image to 100.00. I agree that this could be confusing. The "binary" problem is really strange. I cannot reproduce it. Can you run digikam from console? When you search for similar images, the similarities are logged with the digikam.database: prefix. e.g.: digikam.database: 181148 "42.4814%" Are the values logged also binary? -- You are receiving this mail because: You are watching all bug changes.
