cursor blinking differences in wingui/wincon/vt (fireworks)

[GitMensch]

I've just recognized this the first time and it possibly is "expected", then just close as unplanned;

• wincon/fireworks: slowly blinking "underscore cursor" in lower right (but not blinking regularly - sometimes it is a second, sometimes much faster)
• wingui/fireworks: heavy blinking "pipe cursor" in lower right (but not blinking regularly)
• vt/fireworks: very heavy blinking "pipe cursor" in lower right, blinking "pipe cursor" on upper part of the fireworks parts
• ncurses/fireworks: slowly blinking "pipe cursor" in lower right (but not blinking regularly - sometimes it is a half second, sometimes much faster)

All build with old MinGW, run by double-click (only ncurses demos from within MSYS with TERM='"" cmd.exe /C fireworks).

[Bill-Gray]

I assume that of the first two, one was supposed to be 'WinCon' instead of 'WinGUI'?

Running the WinGUI version in WINE, I get a heavy blinking underscore cursor (which is what I'd expect; should be the bottom quarter of the cell.) I'd expect that in X11 and the SDLs. In all of these, the cursor is drawn by the curses code and should change state every half a second (assuming it gets the chance to do so).

On my Linux box, ncurses, WinCon (in WINE) and VT default to not changing the cursor at startup. (Which is what I'd expect.) The terminal program lets you specify block, underscore, or caret, and whether it's blinking or not. Run testcurs or firework, for example, and the cursor stays that way... until you use the 'output test' in testcurs to get an invisible cursor, then a high-visibility one, then a 'normal' one (where 'normal' is defined as a blinking underscore).

Seeing two cursors in the VT port is pretty weird. Does one move with the mouse? No real idea what's happening there...

The only issue I see with VT's handling of the cursor is that it doesn't restore the initial state when the program shuts down. I just looked into this; I'm not entirely sure it'll be possible to do so.