Page 1 of 1

Prompt on filename collision during renaming

Posted: Tue May 14, 2019 3:12 pm
by 775405984
I suggest Everything can offer a solution for filename collision during renaming files.

Instead of a pop-up window saying there is an error, Everything can give me an option to add a suffix or automatically adds one for me.

Re: Prompt on filename collision during renaming

Posted: Thu May 16, 2019 1:38 am
by void
Everything should do this already for single file renames:


Here I have tried to rename DUPE - Copy.txt to DUPE.txt (which already exists)

I've added to my TODO list: Add an option to resolve rename conflicts by adding (x) suffix or allowing the user to add a custom suffix.

Thanks for the suggestion.

Re: Prompt on filename collision during renaming

Posted: Thu May 16, 2019 1:32 pm
by westernira
it helpful for me. Thanks for the advice.

Re: Prompt on filename collision during renaming

Posted: Thu May 16, 2019 2:12 pm
by NotNull
This is what I see when renaming file1.txt to (the already existing) file2.txt:


2019-05-16 16_09_49-Window.png

Re: Prompt on filename collision during renaming

Posted: Thu May 16, 2019 2:55 pm
by therube
And on XP, F2 rename...
.
Everything - F2 Rename conflict.png

Re: Prompt on filename collision during renaming

Posted: Fri May 17, 2019 8:14 am
by void
Added to my TODO list.

I don't have a simple solution for this. I would like the OS to manage this, but looks like I'll have to implement my own dialog.

https://stackoverflow.com/questions/272 ... -fo-rename

I found the new IFileOperation API to be rather broken.
IFileOperation::CopyFile will abort on the first src not found. -windows 7 x64 sp1
Windows 10 it will attempt to rename the file twice. -try renaming C:\program files\asd3 => C:\program files\asd4 -we get an admin request, the rename happens, and then we fail because we try a second time and C:\program files\asd3 no longer exists. adding a sink does not help.
I too can confirm that the new API does not solve the 80070057 issue on Windows 10 x64 1809.