[digikam] [Bug 369051] Too low similarity threshold in fuzzy/duplicate search bloats the results with potentially unwished high-similarity results [patch]

[Mario Frank]

https://bugs.kde.org/show_bug.cgi?id=369051

--- Comment #3 from Mario Frank <mario.frank at uni-potsdam.de> ---
Hey Gilles,
those are good news. I agree with you concerning the improved usability by
ordering the, as I understand, list of results in the left pane where the
reference image and count of similar images is shown.
But introducing an order here means changing the signature of the functions in
haariface. Since QMap automatically has a sorting on the keys, we could use
this to introduce an order to the result set. One quite easy way would be to
wrap the QMap<qlonglong,QList<qlonglong>> as value of a avg-similarity-map.
This would surely increase the memory consumption during search. But the
automatic ordering by the similarity would circumvent a signifficant increase
of runtime.
After a small glimpse at the source code with grep, I found no possible
conflicts with other files concerning the definition of the result set.
Changing the return value types in haariface should be most likely safe. Should
I propose another patch for this issue?

-- 
You are receiving this mail because:
You are the assignee for the bug.