How to write to the alternate screen buffer on Windows using only the standard libary? about crossterm

[retep998]

Write a wrapper around HANDLE which implements the necessary trait for write! and converts the text to UTF-16 before calling WriteConsoleW.

[TimonPost]

Oke, I have already tried that. If I used escape characters in the string, these were shown as weird symbols.

Example: https://ibb.co/dLTw1d

I use this code. . Any idea why this could be?

[retep998]

In order for newlines and such to be interpreted correctly, the ENABLE_PROCESSED_OUTPUT mode must be enabled on the console screen buffer using SetConsoleMode.

ANSI escape sequences require Windows 10 with the ENABLE_VIRTUAL_TERMINAL_PROCESSING mode enabled, and will never work on older Windows. For older Windows you have to use the API to do things like changing the color.

[TimonPost]

Thanks, I will give it a try. I know that only Windows 10 supports ANSI escape codes. In this crate this option is turned on by default. If the current system does not support this it will fall back to WinAPI. And with this implementation, I got the problem with alternate screen and writing to that alternate screen. But I will try what you have suggested.