TCC36 color anomaly in Windows Terminal.

[vefatica]

I use a color scheme in WT in which color 0 is 00/00/00 and the default background color is 0C/0C/0C. And that's what I get when I start my "TCC36" profile (command line d:\tc36\tcc.exe). As soon as scrolling occurs, the background color changes from 0C/0C/0C (good) to 00/00/00 (bad) at the line where scrolling began. That's hard to see without the help of a debugging tool (easier in person). Below is part of DIR's output in a new TCC36. The debugging tool gives mouseX, mouseY, red, green, blue at the mouse pointer and, below, shows the change before/after scrolling began.

It's the same with any TCC /i startup option and it doesn't happen in other WT profiles, including older TCCs.

These are my TCC36 color options.

I have no clue wnat's going on.

Here's another symptom of the anomaly. Below, the background of the empty line is 00/00/00; the other lines ... 0C/0C/0C.

These are the BTM lines that use ANSI.

The empty line comes from this one.

echo ^e[?25l^e[0m

Then,

echo ^e[?25l^e[0m
echo %@format[15,LOCAL]
echo  ^e[4mHOST^e[0m    ^e[4mOFFSET^e[0m ^e[4mSTRATUM^e[0m  ^e[4mRTT^e[0m

Then in a DO loop,

echo NIST_%i  %@format[7,%offset]    %[stratum]%@format[8,%rtt]

 

[rconn]

TCC will set its startup color, which conhost / openconsole will turn into an ANSI sequence that WT interprets and colors appropriately.

After that, TCC doesn't do anything more with colors (unless you have directory colorization, or you execute a COLOR or CLS), and it doesn't know or care if you're scrolling.

 

[vefatica]

TCC will set its startup color, which conhost / openconsole will turn into an ANSI sequence that WT interprets and colors appropriately.

After that, TCC doesn't do anything more with colors (unless you have directory colorization, or you execute a COLOR or CLS), and it doesn't know or care if you're scrolling.

When TCC "sets its startup color" does it (can it) refer to palette color 0? With my option/color settings default on default seems appropriate.

 

[vefatica]

My WT "TCC36" profile uses the "Ottoson-Custom" color scheme. It is defined like this.

            "background": "#0C0C0C",
            "black": "#000000",
            "blue": "#204DBE",
            "brightBlack": "#808080",
            "brightBlue": "#2F6AFF",
            "brightCyan": "#00E1F0",
            "brightGreen": "#58EA51",
            "brightPurple": "#FC74FF",
            "brightRed": "#FF3E30",
            "brightWhite": "#FFFFFF",
            "brightYellow": "#FFD14E",
            "cursorColor": "#FFFFFF",
            "cyan": "#00A7B2",
            "foreground": "#BEBEBE",
            "green": "#3FAE3A",
            "name": "Ottosson-Custom",
            "purple": "#BB54BE",
            "red": "#BE2C21",
            "selectionBackground": "#92A4FD",
            "white": "#BEBEBE",
            "yellow": "#BE9A4A"

When that profile first starts and I ask for the current color scheme (with 20 OSC ? sequences) I get this.

␛]4;0;rgb:00/00/00␛\␛]4;1;rgb:be/2c/21␛\␛]4;2;rgb:3f/ae/3a␛\␛]4;3;rgb:be/9a/4a␛\␛]4;4;rgb:20/4d/be␛\␛]4;5;rgb:bb/54/be␛\␛]4;6;rgb:00/a7/b2␛\␛]4;7;rgb:be/be/be␛\␛]4;8;rgb:80/80/80␛\␛]4;9;rgb:ff/3e/30␛\␛]4;10;rgb:58/ea/51␛\␛]4;11;rgb:ff/d1/4e␛\␛]4;12;rgb:2f/6a/ff␛\␛]4;13;rgb:fc/74/ff␛\␛]4;14;rgb:00/e1/f0␛\␛]4;15;rgb:ff/ff/ff␛\␛]10;rgb:be/be/be␛\␛]11;rgb:0c/0c/0c␛\␛]12;rgb:ff/ff/ff␛\␛]17;rgb:92/a4/fd␛\

Palette color 0 ("black") was apparently changed by TCC. Is that because of the old Windows bug you once mentioned?