in search not work CTRL+A

[Horst.Epp]

Unfortunately I don't see a good solution here. Either I break input for Asian characters, or Ctrl+A for some users.
I could allow EM_SETSEL when there is no input method editor (IME), but I couldn't find a way to detect whether the current input method uses an IME or not. ImmIsIME(GetKeyboardLayout(0)) always seems to return true even for e.g. German keyboards, maybe because of the Emoji IME, even when it's not active.

Why not making an Ini setting which forces the correct Ctrl-A

[AntonyD]

2ghisler(Author)
could you compile a private build for testing at least some maybe even pseudo logical changes?
like - disable mentioned IME, or revert back some fix, which was applied for better support of CTRL+A in next versions after 10.50b5?
so at least I can test it and report for you - is it the essence of my troubles or there is something more regarding this//////

[ghisler(Author)]

OK, I have sent you a link to a private beta version where I disable Ctrl+A only when a Chinese, Japanese, or Korean keyboard is selected. Only in these cases it would interfere with character input. Please let me know whether Ctrl+A works for you with this version or not. If not, the problem must be elsewhere (e.g. Ctrl+A being intercepted before TC can see it).

[Galajas]

In the new version 10.62 in search (CTRL + S) not working CTRL+A.
In the 10.0 version, everything was good.

How about you, Galajas? Do you still have a problem if you use a clean ini?

Yesterday when updated to 10.52RC5 it started working.
Now again it's not working.

[white]

Yesterday when updated to 10.52RC5 it started working.
Now again it's not working.

But does it work when you use a new ini file?
You can test this by executing the following command on Total Commander's command line:

Code: Select all

"%COMMANDER_EXE%" /N /i="%TEMP%\test.ini"

[Galajas]

Yesterday when updated to 10.52RC5 it started working.
Now again it's not working.

But does it work when you use a new ini file?
You can test this by executing the following command on Total Commander's command line:

Code: Select all

"%COMMANDER_EXE%" /N /i="%TEMP%\test.ini"

No, it's the same, not working.

[petermad]

2Galajas
Does it work right after a reboot of your computer?

[AntonyD]

OK, I have sent you a link to a private beta version where I disable Ctrl+A only when a Chinese, Japanese, or Korean keyboard is selected. Only in these cases it would interfere with character input. Please let me know whether Ctrl+A works for you with this version or not. If not, the problem must be elsewhere (e.g. Ctrl+A being intercepted before TC can see it).

All is perfectly working now)))
All other keys combinations work also perefectly!

P.S. and of course I do NOT have any Chinese, Japanese, or Korean keyboard installed/chosen/etc....

https://www.ghisler.ch/board/viewtopic.php?t=77622
this bug was also fixed;)
I mean - its last part - about Select all. This topic was moved to the sub-forum "TC Behaviour which will not be changed" - but obviously this is already fixed and was changed accordingly and correctly))

[ghisler(Author)]

All is perfectly working now)))

Nice to hear that, thanks for the quick feedback!

P.S. and of course I do NOT have any Chinese, Japanese, or Korean keyboard installed/chosen/etc....

You can actually install one of these via control panel, and switch to it - only then will it stop working, not when it's just installed.

[AntonyD]

You can actually install one of these via control panel, and switch to it - only then will it stop working, not when it's just installed.

I understand, but the point is that I didn’t have these encodings\keyboards, and the code in Total suddenly decided for some reason that it was necessary to work out that piece of it, which should work only when these keyboards were really turned on. And only now - when it was turned off - everything worked for me as it should. Those: either the part of the code that determines whether the listed encodings are enabled / present in the system is partially erroneous, or something is incorrectly set in the system, which makes this code work incorrectly. IMHO so.