I really like the TCC screen output speed. However, I think it could be even faster with buffered output, for example:
1) Screen buffer is kept in ram
2) If a change occurs in the screen buffer, it's outputted to the visible window at current monitor refresh rate
3) scroll bars could reflect ram screen buffer (rather than actual visible screen)
Would that work? For example, if I record time of relative large directory listing with
timer /1 ON && dir /sa && timer /1 OFF
it takes 2,76 seconds on first run (filling the buffer and adjusting scroll bars) and ~0,8 seconds on subsequent runs. However, the same command with NUL piping (see below) takes only 0,11 seconds:
timer /1 ON && dir /sa >NUL && timer /1 OFF
comments or thoughts?
1) Screen buffer is kept in ram
2) If a change occurs in the screen buffer, it's outputted to the visible window at current monitor refresh rate
3) scroll bars could reflect ram screen buffer (rather than actual visible screen)
Would that work? For example, if I record time of relative large directory listing with
timer /1 ON && dir /sa && timer /1 OFF
it takes 2,76 seconds on first run (filling the buffer and adjusting scroll bars) and ~0,8 seconds on subsequent runs. However, the same command with NUL piping (see below) takes only 0,11 seconds:
timer /1 ON && dir /sa >NUL && timer /1 OFF
comments or thoughts?