Handling of file comments (descript.ion)

[ktibor]

Handling of file comments (descript.ion)
This is an old problem: if the target directory already contains a descript.ion, the user cannot copy descript.ion from the source directory (nothing will happen when copying). This is an annoying behaviour in case of many new or modified comments in the source directory, while the "real files" are not modified. The Synchronize Directories function handles comments in the same way. This is far more serious: on the backup drive, only comments related to new/modified files will be refreshed or created. New/modified comments belonging to unchanged files will be lost. In my opinion, in Synchronize Dirs it would be better to handle the descript.ion-s as normal files.

[ghisler(Author)]

You can configure this yourself: If you choose "Copy comments with files" in Configuration - Options - Operation, the descript.ion files themselves will not be copied. Instead, the comments will be copied when the files are copied. Otherwise the descript.ion files will be treated like normal files.

[ktibor]

Thank you, this was already clear. I try to explain the problem in other words: I wish to keep the setting "Copy comments with files"=Yes since this is the behaviour I need when copying and moving. Moreover, I would expect the backup drive actualized by "Synchronize Directories" to contain exactly the same as the source drive. It's a pity this requirement is not met because the "Synchronize Directories" does not transfer the new/modified file comments when the files themselves are unchanged - and this is not a rare case. What can a user do to keep all file comments in safety?

[ghisler(Author)]

Unfortunately this would only be possible in asymmetric mode - otherwise TC couldn't know which comment is the newer one because there can be multiple comments in a descript.ion file, so the timestamp doesn't tell us which individual comments are newer.

[ktibor]

Many thanks for your answer.
I am close to the solution: I always met the subject problem when I synchronized the work drive with the backup drive in asymmetric mode. Let us suppose the following: File comments are created/modified only on the work drive (TC Ctrl+Z), whereby the descript.ion-s here are always newer or the same compared to those on the backup drive.
In the first step, at Options / Operation / File comments - Preferred type I change to files.bbs, thus the descript.ion-s lose their privilegized status.
In the second step I perform an asymmetric synchronization. At this point also the newer descript.ion-s appear in the left side list, making their copying possible.
In the third step I reset the Preferred type to descript.ion (if I do not forget about it ).
This procedure really solves my problem, maybe it is slightly complicated.
If you cannot offer a better solution, let us consider this problem solved.

[ghisler(Author)]

OK, this isn't something which can be added over night. I will add it as a suggestion to my to do list for a later version.