[TC11.03] Cursor position does not move to new file in filelist when I copy a new file with SHIFT+F5

[pokapolo]

Until TC 11.02, when I copy a new file with SHIFT-F5, then TC moves the cursor position to new copied file.
However, TC11.03 does not move cursor, and it is still on the source file.

I prefer the operation of TC 11.02.
How can I solve this problem ?
Is there any configuration setting ?

[sa16]

2pokapolo
Maybe, SHIFT+F5?

Behavior changed in TC11.03RC3.

[white]

Maybe, SHIFT+F5?

Behavior changed in TC11.03RC3.

Confirmed.

[pokapolo]

Yes, SHIFT-F5 (F4 is mistype, sorry).
Thank you for your answer.
The older behavior is better for me, but somebody feels not.
I think it is better to make it configurable.

[white]

Yes, SHIFT-F5 (F4 is mistype, sorry).

You can edit the first post and change it. Changing the subject of the first post will also change the topic title.

The older behavior is better for me, but somebody feels not.

There is no mention in HISTORY.TXT of this change, so I assume the change is unintentional.

[petermad]

I can confirm the change from TC 11.03rc3 and forward.

the only change I see in the history for TC 11.03rc3 about copying is:

26.01.24 Fixed: Copy in background (AlwaysCopyInBackground=1) would incorrectly move the caret (cursor position) in the source panel (32/64)

but I do NOT use AlwaysCopyInBackground=1

[ghisler(Author)]

Yes, that's the change which caused it - TC tries to stay on the file before moving files, and copying and moving share the same function.

[efesreal]

Can you make old behaviour is optional

[Olfert]

I'm a heavy user of using shift+F5 for making a new version of a file I'm about to edit. This "new feature" just caused me to loose an important file as I edited the original instead of the new file... Any way to get the old behavior back? (apart from running an older version...)

[Fla$her]

Can you make old behaviour is optional

I don't think there are any difficulties in comparing copying and moving. Surely there is a flag by which it is possible to easily distinguish one from the other. The author most likely meant that the described behavior for both operations occurred unintentionally.

This "new feature" just caused me to loose an important file as I edited the original instead of the new file...

How can it cause loss if it’s copying, not deleting?

[JOUBE]

Yes, that's the change which caused it - TC tries to stay on the file before moving files, and copying and moving share the same function.

2ghisler(Author)
Please restore the previous behavior - optionally if there is not other way.

[Olfert]

How can it cause loss if it’s copying, not deleting?

It's part of a well choreographed keyboard routine with years in muscle training:
When I am about to make changes to a file, I first make a new version (using the shift-F5). Then I hit enter to edit the file (file opens in the associated program).
Then after finishing the edit of the new file I often delete the original. But in this case I wasn't happy with the edit (which was happening to the original file this time) and after closing the edit I deleted the new copy (which was the unedited version this time) and ended up with an edited "original" file.
Does that make sense?

[Horst.Epp]

When I am about to make changes to a file, I first make a new version (using the shift-F5). Then I hit enter to edit the file (file opens in the associated program).
Then after finishing the edit of the new file I often delete the original. But in this case I wasn't happy with the edit (which was happening to the original file this time) and after closing the edit I deleted the new copy (which was the unedited version this time) and ended up with an edited "original" file.
Does that make sense?

Strange behavior to edit files.
Every useful editor makes backups of the edited file.
So there should be no need to first make a copy.

[Olfert]

Strange behavior to edit files.
Every useful editor makes backups of the edited file.
So there should be no need to first make a copy.

The "editor" is Indesign. So no backup after editing...
- and that is beside the point that a valuable feature (at least for me) has changed in TC.

[SlavoFolk]

Please be sure to restore this option or make it configurable. For so many years, I got used to the fact that after copying a file under a new name, the cursor was on the new file and I always reflexively opened it with the enter key. Due to this change, I have already lost my job several times (including a fragment of the book I am writing) because I was editing the wrong file...