When I tick 'name' and 'size' for dupes search, that should mean exactly that: dupes are defined as such if their name AND size match. For instance:
-it makes no sense assuming a file_p1.rar is a dupe with file_p2.rar just because they have the same size. They're on the same folder, they CAN'T be the same!
-if I suspect there's a reason for the described rare situation being true, ie, different names being twin files, there's 'content' search which by design is considerably slower.
-it makes no sense having a large list of false positives due to current comparison scheme as it completely makes null the dupes column right click options: it's a PITA having to deselect each and every one of them out of a generally large list of results.
As we have folder comparison on a foreseeable timetable it also makes sense contemplating these questions now.
AND-driven comparison logic for dupes search
AND-driven comparison logic for dupes search
Power-hungry user!!!
Re: AND-driven comparison logic for dupes search
I'm pretty sure that is already how it works.
Can you post a screenshot showing the "incorrect" results?
Given:
Dupes using Name (Ignore Extension):
Dupes using Size:
Dupes using Name (Ignore Extensions) & Size:
Dupes using Name (Ignore Extensions) & Size & Date:
Can you post a screenshot showing the "incorrect" results?
Given:
Code: Select all
A\ a.txt 0 bytes 6/30/2016 8:29:38 AM
A\ a-only.txt 0 bytes 6/30/2016 8:29:38 AM
A\ c.txt 5 bytes 6/30/2016 8:29:38 AM
B\ a.bak 0 bytes 5/30/2016 8:29:38 AM
B\ a.txt 0 bytes 6/30/2016 8:29:38 AM
B\ b.txt 0 bytes 6/30/2016 8:29:38 AM
B\ b-only.txt 0 bytes 6/30/2016 8:29:38 AM
C\ a.txt 31 bytes 6/30/2016 8:29:38 AM
Code: Select all
1: B\ a.txt 0 bytes 6/30/2016 8:29:38 AM
1: A\ a.txt 0 bytes 6/30/2016 8:29:38 AM
1: B\ a.bak 0 bytes 5/30/2016 8:29:38 AM
1: C\ a.txt 31 bytes 6/30/2016 8:29:38 AM
Code: Select all
1: B\ a.bak 0 bytes 5/30/2016 8:29:38 AM
1: A\ a.txt 0 bytes 6/30/2016 8:29:38 AM
1: B\ a.txt 0 bytes 6/30/2016 8:29:38 AM
1: A\ a-only.txt 0 bytes 6/30/2016 8:29:38 AM
1: B\ b.txt 0 bytes 6/30/2016 8:29:38 AM
1: B\ b-only.txt 0 bytes 6/30/2016 8:29:38 AM
Code: Select all
1: A\ a.txt 0 bytes 6/30/2016 8:29:38 AM
1: B\ a.bak 0 bytes 5/30/2016 8:29:38 AM
1: B\ a.txt 0 bytes 6/30/2016 8:29:38 AM
Code: Select all
1: A\ a.txt 0 bytes 6/30/2016 8:29:38 AM
1: B\ a.txt 0 bytes 6/30/2016 8:29:38 AM
Re: AND-driven comparison logic for dupes search
Will do, thank you for listening.
Power-hungry user!!!