Show Posts
1
Feature Requests and Suggestions / Option to Use Standard Win10 Copy/Replace
« on: November 21, 2015, 22:31:29 »
Hello:
First, thank you for a great piece of software!
I wanted to suggest that you allow the option to use Windows Copy/Move rather than the built-in script. While this may be a little slower, Microsoft has really improved Copy/Move behavior in recent versions of Windows (even Win8). In particular, the built-in script will wait for user intervention whenever it encounters a filename collision in the source and target directories, asking whether to skip or replace, but it stops all other valid file copying that doesn't require user input until this is resolved. Needless to say, it happens quite often that I'll copy a directory with a large number of files to a directory with existing files, go away expecting the process to complete in 5 or 10 minutes, then come back to find the copy operation stuck at 5% because of a filename collision. There's no guarantee that this will not happen again once it encounters another collision at 7% or 10%, etc. requiring constant user supervision for a task that should be left alone.
The correct behavior, which is what Win10 does, is that the copy operation proceeds fully and only those files that have filename collisions are left pending user intervention. That way, if you go away for 10 minutes, the 30GB file transfer is essentially completed, pending a user resolution for a small handful of files. Also, win10 allows you to display a comparison of file features to help you resolve the filename collision, and offers a check-box to use the same resolution for all remaining collisions.
Thanks!
First, thank you for a great piece of software!
I wanted to suggest that you allow the option to use Windows Copy/Move rather than the built-in script. While this may be a little slower, Microsoft has really improved Copy/Move behavior in recent versions of Windows (even Win8). In particular, the built-in script will wait for user intervention whenever it encounters a filename collision in the source and target directories, asking whether to skip or replace, but it stops all other valid file copying that doesn't require user input until this is resolved. Needless to say, it happens quite often that I'll copy a directory with a large number of files to a directory with existing files, go away expecting the process to complete in 5 or 10 minutes, then come back to find the copy operation stuck at 5% because of a filename collision. There's no guarantee that this will not happen again once it encounters another collision at 7% or 10%, etc. requiring constant user supervision for a task that should be left alone.
The correct behavior, which is what Win10 does, is that the copy operation proceeds fully and only those files that have filename collisions are left pending user intervention. That way, if you go away for 10 minutes, the 30GB file transfer is essentially completed, pending a user resolution for a small handful of files. Also, win10 allows you to display a comparison of file features to help you resolve the filename collision, and offers a check-box to use the same resolution for all remaining collisions.
Thanks!