Solved [TC 10.52rc1] cm_exit 1 shows the instance # [2] in the Title of the TC window

[Elwin_Ransom]

After restarting the 64-bit version of TC 10.52rc1 with cm_exit 1, the instance number [2] appears in the title of TC window.

— This happens all the time on my working copy of TC with many plugins installed.
— On a clean copy of TC without plugins, it happens much less often.
— On the 32-bit version, it doesn't happen — the window title remains clean after restarting.

[petermad]

I have seen it happen occasionally on 64bit TC on Windows 7

[ghisler(Author)]

Unfortunately this cannot always be avoided. TC has to call the ShellExecuteEx command while it is still running, so the new instance may be there faster than TC can close itself.

[white]

Unfortunately this cannot always be avoided.

Unless you add a parameter to set the instance number and always set the instance number of the restarted TC to the same instance number of the currently running TC.

[ghisler(Author)]

That would be strange if instance 3 restarted and the other instances had been closed in the meantime...

[Fla$her]

Unfortunately this cannot always be avoided. TC has to call the ShellExecuteEx command while it is still running, so the new instance may be there faster than TC can close itself.

If you can't even fix it, then the point in restarting in this way with resident additions tied to the process disappears altogether. It's better to use scripts.

[white]

That would be strange if instance 3 restarted and the other instances had been closed in the meantime...

You can check for that too.

[Elwin_Ransom]

Anyway, I would prefer to use scripts if there is no way to avoid the instance number in the title bar.

[ghisler(Author)]

I found a better solution: Start the new instance only once the old window has been destroyed. It may make the restart a bit slower, but there will be no problem with instance numbers.

[Fla$her]

I found a better solution

I would say the only true one. Or do you distinguish a window from a process?

[petermad]

10.10.22 Fixed: CM_EXIT with restart parameter now waits with launching a new instance until the window has been deleted (32/64)

Confirmed fixed in TC 10.52rc2 - I have not been able to provoke a new instance number with cm_Exit 1

[Elwin_Ransom]

Very nice. Thanks for the fix.