Warn about deleting fuzzy matches
Reported by Virgil Dupras | October 27th, 2010 @ 09:37 AM
Split from #111
When user runs software for the first time, make it clear that it is using fuzzy logic for matching, or at least warn the user about this before deleting any files. I nearly deleted a load of PDF's because they had a similar preview image, yet the filesizes were different
Comments and changes to this ticket
-
Virgil Dupras October 27th, 2010 @ 09:48 AM
The default scan for dupeGuru is an exact matches scan, not a fuzzy one. The user has to chance the preferences himself, which I find a pretty good warning in itself.
But then, if we really wanted to warn the user, there could be a message that pops up whenever one of the deleted dupes have a less then 100% match that says "Warning, some of the duplicates you're about to delete are not 100% matches. You should review your results before proceeding", with an option "Don't show this dialog again".
-
carpii October 27th, 2010 @ 04:26 PM
Oh, I see.
I was fairly sure that after installing DupeGuru PE for the first time, it was straight away using fuzzy matching (mine was set to around 80% I think).I wonder if I had installed the software a while ago, then uninstalled, and it remembered my settings from then.
I guess this a bogus report, sorry :)
-
Virgil Dupras October 31st, 2010 @ 11:03 AM
I'm not so sure it's a bogus idea altogether. People might play with preferences not realizing what they're doing. A warning on the first time they delete dupes that aren't 100% matching might prevent hurtful deletions. I'll keep this ticket around.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
People watching this ticket
Tags
Referenced by
- 111 Show object id in Power Marker mode I split this ticket into separate ones: #113 #114 #115