Not reproducible here.> Click on TCmds red X or file/exit achieves nothing.
> If I exit every tab I am still left with an empty shell. Must
> close in TaskManager
> Click on TCmds red X or file/exit achieves nothing.
> If I exit every tab I am still left with an empty shell. Must close in
> running 13.00.19 x64 under win7-64
Try the test build in ftp://jpsoft.com/beta/tcmd.exe and let me know if it> I have TCMD set to remain open if it has no tabs. Whenever I "X" a tab,
> it takes 4+ seconds for the TCC process to disappear from TaskMgr; if it's
> the only tab it takes 4+ seconds for it to disappear from the TCMD
Interesting, because there were *no* other changes in the shutdown code.> It did not change the behavior described above and it did bring back
> the old shutdown delay.
Assuming that TCC 11 is running with the same configuration as 12 and 13,> TCC 11 also terminates immediately. And TCMD (v13) terminates
> immediately when X'ed if TCC v11, CMD, or PS is the only thing
> running in a tab.
Yes, and yes.> What happens when the user X's a tab (or X's TCMD)? Do you send
> WN_SYSCOMMAND\SC_CLOSE to the console? Are you sure it's sent right
None of the above. TCC is apparently hanging (only on your system?) in an> If you've got it, please tell me ... what was it's (crazy?) dependence
> on TCEXIT, UpdateTitles, and TITLEPROMPT?
Try it one more time with the new build 21 (you'll have to uninstall first;> Both problems are gone in build 21.
Try it one more time with the new build 21 (you'll have to uninstall first;
it takes me a couple of hours to create a new build rev) in the ftp beta
I've shuffled around some of the shutdown code and added a couple of sanity
checks. I think your problem was strictly timing related; you were just
unfortunate enough to be in the wrong place at the wrong time during