Bug found in auto-rename

[Nazaren0]

Hello,

there seems to be a bug with the auto-renaming system. I've tried to find a setting in the configuration options, but it seems it's not possible to customize this behavior.

Example:

Original name: "Sales Report (2016) - First Rev.txt"
Auto-renamed as: "Sales Report (2017) - First Rev.txt"
Should be auto-renamed as "Sales Report (2016) - First Rev (2).txt"

Regards

[sa16]

I confirm (when copying).
In MRT, the file is renamed correctly.

[petermad]

Confirmed too.

[ghisler(Author)]

This isn't a bug, it's how the function works - it looks for a number in braces and increases it by one.

In MRT, the file is renamed correctly.

What do you mean? Isn't the report is about mrt?

[sa16]

What do you mean? Isn't the report is about mrt?

It seemed to me that the report on the commands cm_Copy or cm_Rename, if the "Auto-rename copied", "Auto-rename target files" overwrite option was selected.

[petermad]

if the "Auto-rename copied", "Auto-rename target files" overwrite option was selected.

That is my impression too. And my confirmation of the problem regards copying with these options selected

[Nazaren0]

This isn't a bug, it's how the function works - it looks for a number in braces and increases it by one.

Any option or review to include a setting in the auto-rename feature like "force rename only at end of filename" ?

[Galizza]

Original name: "Sales Report (2016) - First Rev.txt"
Auto-renamed as: "Sales Report (2017) - First Rev.txt"

If you read the names of the Original & Auto-renamed files, in my opinion it is a bug and a quite dangerous one.

The original file must be auto-renamed as "Sales Report (2016) - First Rev (2).txt"

[white]

If you read the names of the Original & Auto-renamed files, in my opinion it is a bug and a quite dangerous one.

I think that the auto-rename options in the overwrite dialog was designed to be flexible when it was added 20 years ago to TC 7. The last number between brackets anywhere in the filename is increased (even when the number is in the filename extension).

[sa16]

Users expect auto-renaming to follow the rules in Help:

Auto-rename copied
When a name collision occurs, the copied/moved files will be renamed automatically in the form filename(1).ext, filename(2).ext etc.
Auto-rename target files
When a name collision occurs, the existing target files will be renamed automatically before copying/moving the source files, in the form filename(1).ext, filename(2).ext etc.

and according to the parameter:

AutoRenameMode=3 Determines how files are auto-renamed when copying or in multi-rename tool. Sum of:
1: append number (x) separated by space, e.g. name (2).txt instead of name(2).txt
2: start number at (2), not (1), e.g. name.txt, name (2).txt etc.

[Fla$her]

There is no doubt that parentheses with a number should be searched at the end of the base name and nowhere else.

[white]

How about numbers with leading zeros? Currently it works like this:

Existing name:
name (001).txt

Auto renamed:
name (2).txt

[Galizza]

How about numbers with leading zeros? Currently it works like this:

Existing name:
name (001).txt

Auto renamed:
name (2).txt

This option is far from ideal, but if we want prioritize security to the maximum.

Existing name:
name (001).txt

Should be auto renamed:
name (001)(2).txt

This would basically be following what is indicated in Help to the letter.

[petermad]

There is no doubt that parentheses with a number should be searched at the end of the base name and nowhere else.

I agree.

[AntonyD]

Should be auto renamed:
name (001)(2).txt

I also fully agree on that.