Motorocker wrote:TLis wrote:You might delete by mistake the wrong file ...
I can't delete
wrong file, because it is FULL duplicates.
Yes, you can. Usually, you want the file in the particular folder, don't you? By deleting one of the duplicates 'by position' in the result list you are quite likely to delete the one, that you have actually wanted to keep, which would force you then to move the remaining files to the right folders. Example:
Code: Select all
---
C:\Photos\Poland\a1.jpg
C:\Poland\a1.jpg
---
C:\Germany\a2.jpg
C:\Photos\Germany\a2.jpg
---
Of course, I would like the photos in C:\Photos subfolders to remain, but here I would definitely delete the wrong one, if I follow your suggestion.
Samuel wrote:This preselection could perhaps bring a noob to waste his OS by searching his C:\ for files with same name (not size and content) and afterwards delete them. But what could prevent a noob to do so, if he just selects the files manually. Mh he would destroy his system slower.
Implementation of this feature is just a direct invitation leading to serious problems. Probably, a noob would never destroy his OS like that, if he had not had this feature in TC
Such a long list needs to be scanned thoroughly, before proceeding. Usually, you analyse it in chunks, deleting the duplicates, which aren't necessary.
If this feature is implemented, I would expect, that a serious warning is displayed about the automatic way, in which the files were marked, and the consequences of removing wrong files.