https://bugs.kde.org/show_bug.cgi?id=491599
--- Comment #3 from Roland <carbonwer...@hotmail.com> --- Hi Mark Thank you for the correction on my understanding of how the default Del works for duplicates. I would suggest the behavior as it is implemented is probably a logical bug. There is a mechanism for defining the reference image during the filtering. That is, this is not arbitrary, and I think it would be reasonable to expect that the system would not default to deletion of the reference image. Of course, it may be that the user wishes to delete the reference image, but that could just be intervention in the form of a manual selection of which duplicate(s) to delete for that list entry. Its not sarcasm when I ask- what is the purpose of defining a reference image in a function like this if the reference image isnt intended to be special in some way? That is, if there are filters to define Reference as 'prefer newer date' or 'larger image' or 'newest modified', the implication is that the user considers those to be primary against which other instances are assumed to be duplicates. In my view, it would be best to simply always place the reference image at position 1 in the summary view, and have the focus for 'delete' on the first non-reference image. In a scenario where someone runs a Similarity check against 1 or more albums, it is possible to simply hit the 'remove duplicates' button as a batch process, and it isnt at all clear from that: if duplicates arent defined as non-reference, then this is doing something that isnt implied (at least, not to me). Best Rob -- You are receiving this mail because: You are watching all bug changes.
