Sychronize Dirs: Overwrite, Esc -- neither file on target

[Ralph]

If I synchronize directories and allow a target file to be overwritten, but then stop copying by pressing Esc, the target file already will be gone. The behavior may be intended, but I think it would be more cautious if TC could delete at the last moment or inform the user. Steps:

. Synchronize directories. The source and target directories should contain a file with the same name, but the target file should be older and smaller. The source file should be large, so there will be enough time for interrupting the process.

. Respond OK when TC asks whether to overwrite the target file.

. Press the Esc button to stop the copying and then OK to confirm that copying should end.

. The target file will be gone. If I try to stop copying, the reason may be that I have reconsidered and want to look at the target file. Also, if a user interrupts copying, the user probably will assume that either the old or new file exists in the target directory. Therefore, I would prefer that the target file not be erased until TC has copied to a temporary file and is ready to rename it, or that TC warn that the target directory now contains neither the source file nor the target file.

Total Commander 8.51a, 64-bit.
TC Configuration, Copy: Standard copy method.
Windows 7, 64-bit.

Thanks

[ghisler(Author)]

When you confirm the overwrite, TC will truncate the already existing file and write the new data. This is necessary so all the metadata like attributes, extra streams, comments, etc. are preserved.

[Ralph]

Thanks for your explanation.

I think it would be helpful if TC could tell the user which file was being copied when the process was stopped, and mention if the target file was removed. The user could take that information and copy the source file to the target directory, if desired; it may be better to have the source file than nothing for that file in the target directory. TC's behavior is logical, given the explanation, but it was not obvious to me in advance. There may be other users who assume that the target file is removed at the end of the copy, not the beginning. If the user stopped the copying, the user also may exit from Synchronize Dirs before the directory comparison has been refreshed, so the user may not see that indication of lack of copying.

Thanks