When overwriting a file, TC forgets to delete it's comment

[m^2]

1. Create files C:\1 and C:\2
2. Add some comment to C:\1
3. Rename C:\2 to C:\1
Result: The new C:\1 has a comment from the old one.

I'm not sure if it's an omission or was it designed this way, but nontheless it was unexpected and certainly not natural for me. I feel that a comment is bound to a file, not to it's name. And actually renaming the other way (C:\1 to C:\2) keeps the comment with file.

[ghisler(Author)]

By default, comments are not copied with files, except when you enable it in Configuration - Options - Operation - Copy comments with files.

Even then it only works when you don't use the Explorer copy or delete methods...

[m^2]

I should have mentioned it - I have TC configured this way.

[Balderstrom]

When file 1 exists, and file 2 overwrites it -- and file 2 has a comment as well as file 1.
I'd think the best/optimal behaviour would to provide the user a dialog to find out which comment is correct.

But the above is how it's always worked afaik, the comment is bound to the fileName, normally it would update the comment to match what the new fileName is.

Apparently that part of the comment-change code doesn't get triggered when the new-file-name overwrites an old file, and the old-file has a comment.

It also occurs, if you have Explorer mode enabled for delete. (the descript.ion doesn't update after delete)

Copy01.txt -> Comment: Copy01
Copy02.txt -> Comment: Copy02

Delete Copy01.txt
Now uncheck Explorer delete method, just in case.

Rename, Copy02.txt to Copy01.txt

Copy02.txt -> Comment: Copy01