Fixed TCMD Screen Buffer Not Working Correctly in Build 19

[Jay Sage]

A new problem has appeared with build 19. When TCMD launches, the initial TCC tab cannot be scrolled back to see the output that was generated during the startup process. In fact, after generating addition output, the tab still cannot be scrolled back. It's as if the screen buffer has no more lines than the rows of the TCMD screen. But I checked, and the buffer is set to the default 5000 rows.

Is anyone else seeing this?

 

[Jay Sage]

The problem persists when I detach the TCC session. However, if I launch a standalone TCC session (that never runs inside TCMD), the screen can be scrolled. If I attach that TCC session to TCMD, I can no longer scroll the screen.

 

[Jay Sage]

One more update. Once a TCC session has been attached to the newly launched TCMD, it can no longer be scrolled, even after it is again detached. I started a TCC32 session and observed the same thing. TCMD33b19 kills the ability of TCC screens to be scrolled.

 

[rconn]

Are you running a dark theme? (Or is your Windows theme dark?)

And are you running the legacy console?

 

[Jay Sage]

No dark themes, and I'm not sure what you mean by "legacy console". I certainly have not done anything to install any special console. It's whatever I've been running all along.

I did just start up TCMD32, and it works fine. TCMD32 and TCMD33 share a common TCSTART file, so it did not get corrupted somehow.

Can you think of any experiments I can try? Is there a way for me to back up to build 18? I tried running its install file, but it simply complained that I was already running a newer build. If possible, I'd like to avoid uninstalling version 33 and starting from scratch, since it takes a good bit of work to get new versions configured. (It really would be nice if all the settings could be written out to a file that could be imported into a new version.)

 

[rconn]

No dark themes, and I'm not sure what you mean by "legacy console". I certainly have not done anything to install any special console. It's whatever I've been running all along.

I did just start up TCMD32, and it works fine. TCMD32 and TCMD33 share a common TCSTART file, so it did not get corrupted somehow.

Can you think of any experiments I can try? Is there a way for me to back up to build 18? I tried running its install file, but it simply complained that I was already running a newer build. If possible, I'd like to avoid uninstalling version 33 and starting from scratch, since it takes a good bit of work to get new versions configured. (It really would be nice if all the settings could be written out to a file that could be imported into a new version.)

Try updating to 33.0.20 (already uploaded). I could reproduce your issue about 5% of my attempts -- I tracked that down to a Windows console API setting window & buffer values, a subsequent Windows API sometimes getting the old values (unless a wait was inserted, like when debugging, or if the subsequent API was called again until it returned the updated values). I added a workaround to build 20l let me know if it fixes your issue.

All of the settings can be written out to a file; see the XMLSettings .INI directive in the help.

 

[Jay Sage]

Problem fixed. Thank you. (And the help window still remembers where I put it last time.)

For me the problem had also been intermittent, but it was happening almost all the time, so much so that I wasn't sure that I was remembering correctly when I thought it had worked OK once or twice.