cm_exit 13 - inactive window (for TCx32 only)

[monarch-lfv]

Problem: when restarting the TC with the command "cm_exit 13", Total commander turns out to be an inactive window, that is, it loses focus on other open applications. Moreover, the problem appears only on TCx32 version 11 (I don’t know which beta it started with). There was no problem on TC 10.52x32 either.
The problem can be reproduced on a pure TСx32 as follows:
Run the following command on the command line:

Code: Select all

cmd /C "Timeout /T 1 >nul"

and then this one:

Code: Select all

cm_exit 13

[Horst.Epp]

Not confirmed.
TC x32 restarts, gets the focus and works as usual.

[monarch-lfv]

2Horst.Epp
Maybe Windows is to blame? I have Win7x64.
In general, as far as I understand, the problem occurs when the program passes the command to the child process. In my example:
TC -> cmd -> Timeout

[Fla$her]

2monarch-lfv
Have you checked with /i=cleared.ini ?

[ghisler(Author)]

It may be a timing problem on your PC - if a program takes too long to start, it may not gain the focus.

[monarch-lfv]

I tested on a working computer (Win10x64). Unfortunately, the problem is also present.
Thus, there are a problem on different machines. I ask forum users to check again, please. It may not work every time, try 2-5 times in a row.
I also repeat: the problem appeared in the version of TC11x32. Version 10.52х32 did not have a problem.
The file WINCMD.INI for the test was deleted completely. At the first launch, the TC creates a new file WINCMD.INI , that is, completely clean and standard.

[Sir_SiLvA]

not confirmed here either, Windows 10 with 32bit and 64bit.
TC has the focus always after restart.

[monarch-lfv]

Hmm, strange, well. If this is manifested only with me, then I will live on with this or look for the cause of the problem.

[petermad]

2monarch-lfv

I can confirm it with 32bit TC 11.00 under Windows 7 and under both 64bit and 32bit TC 11.00 under Windows 10.

EDIT - it only sometimes that I can reproduce it with 64bit TC, and I haven't found a way to reproduce it with 64bit TC.

[ghisler(Author)]

Unfortunately it's a Windows problem. I don't think that there is anything I can do about it, sorry.

[monarch-lfv]

2ghisler(Author)
Well, then why was this problem not in version TC10.52 x32? Accordingly, something has changed in the 11th version.

[ghisler(Author)]

I have compared the code, CM_EXIT was not changed between TC 10.52 and TC11.00. As I wrote, it's probably a timing problem: Windows allows to run programs in the foreground only from programs which are already in the foreground (in this case, the previous instance of TC). However, there is a small timeout of a few seconds: If the new program doesn't start quickly enough, Windows doesn't let it in the foreground when the launcher program is no longer in the foreground (it closed). My guess is that your virus scanner doesn't trust TC 11.00 yet (but it trusts 10.52), so it takes longer to start.

[ghisler(Author)]

Moderator message

Moved to will not be changed