[TC 11.00b4] Right arrow not working when renaming a file

[unter_officer]

Hello.
I apologize for my English, forced to to use Google Translate.

Windows 7 Enterprise (64-bit).
TC 11 beta 4 (32-bit). On 64-bit version TC the bug is not reproduced.

If in wincmd.ini CtrlArrow=1, then the bug appears.
If in wincmd.ini CtrlArrow=0, then there is no bug.

How to reproduce the bug:
Set in wincmd.ini key CtrlArrow=1.
Press Shift+F6, then press "Home" to move the cursor to the beginning of the filename.
After that, the cursor does not move to the right!

[Fla$her]

TC 11.00b3-4 x32
With CtrlArrow=1, the right key (also with modifiers) doesn't work only before the first and second characters.

[unter_officer]

Addition to my first post.
Presumably the bug began to appear after this:

15.05.23 Fixed: Cursor movement in rename box (Shift+F6) would jump by 2 characters instead of one when using a dual byte locale like Korean (32/64)

[petermad]

Hmm, I cannot reproduce this. Tested with TC 11.00b4 32bit on Windows XP, 7 and 10 with normal and with fresh wincmd.ini file.

Also tested with RenameSelOnlyName set to 0 and 1. Tested under Danish locale and with files with ANSI-names

[unter_officer]

2petermad
I have this bug reproduced on five computers.

Also, on the Russian-language forum, this bug was reported by another user.
It is not yet possible to understand the reason why someone has this bug, but someone does not.

[petermad]

Also, on the Russian-language forum, this bug was reported by

Maybe it is a locale problem, or a character encoding problem. Does it happen for you on files with only Latin charaters?

[Fla$her]

This is clearly a problem with the locale. The characters in the names don't matter. These can be numbers, punctuation marks, etc.

[unter_officer]

Does it happen for you on files with only Latin charaters?

Yes.

[ghisler(Author)]

Set in wincmd.ini key CtrlArrow=1.
Press Shift+F6, then press "Home" to move the cursor to the beginning of the filename.
After that, the cursor does not move to the right!

Unfortunately I cannot reproduce that, sorry.
I have tried the following:
1. Started Windows 7 virtual machine
2. Changed locale for non-Unicode programs to Russian (Russia)
3. Rebooted as requested
4. Started Total Commander 32-bit with parameter /i=c:\test\test.ini, where the ini file only contained
[Configuration]
CtrlArrow=1
5. Pressed Shift+F6 on a file
6. Pressed Home
7. Pressed right arrow
-> the cursor moved 1 character to the right as expected.

Maybe I'm missing something?

[unter_officer]

Maybe I'm missing something?

No, everything is correct.

We are discussing this bug in two Russian-language forums. At the moment, the bug has only been confirmed in two people.
I have this bug reproduced on five computers.
So far, we cannot understand the reason why someone has a bug, and someone does not.

[Fla$her]

2ghisler(Author)
Conflict with the TwinKey plugin (without settings).

[unter_officer]

2Fla$her
I don't have TwinKey.

2ghisler(Author)
Installed Virtualbox, launched Windows 7. There is no bug.
I assume that the problem is in some individual OS settings on real machines.

[Fla$her]

There is also a problem with the Autorun plugin. autorun.cfg:

Code: Select all

LoadLibrary Plugins\Autorun_Tweaks.dll
SetMessageAction 12345 Set Test 1

Both plugins separately cause a problem for the last 2 betas.

[ghisler(Author)]

2unter_officer
The beta test will still go on for a while, so hopefully we will find what is causing it.

[Fla$her]

2ghisler(Author)
I can't reproduce the bug either on both clean TC or with the current Configuration without the plugins specified.
Maybe, if you manage to reproduce and fix the problem with plugins, then without them, everything will work for the rest.

There is a high probability that the problem is related to the call of the WH_CALLWNDPROC hook. Twinkey apparently does that too. The author of Autorun confirmed the problem on Win 10 1809 x64 with TC 11.00b4 x32.