Disable Console.Clear() in NetConsoleDriver

[CarrnellTech]

Description

Feature request to disable Console.Clear() when application exits.

I suspect this is the line. (Forgive me if I'm wrong as I am very new to C# programming.)

ConsoleEx/SharpConsoleUI/Drivers/NetConsoleDriver.cs

Line 602 in 7191cb6

Console.Clear();

I rather like the original console being preserved even after it exits. It would be a handy choice to have in the driver.

(Note, i am not sure what the difference of Direct vs Buffer is. I tested it and see no difference. Its my understanding that buffer was a separate terminal screen in order to not junk up or make an unnecessary history on the normal one. I am pretty sure I am wrong tho. Still new to a lot of this.)

Please and thank you!

Use Case

This would give people more control for the console to be preserved, no matter the type of render mode they use. At least that's my hope.

Proposed Solution

ConsoleEx/SharpConsoleUI/Drivers/NetConsoleDriver.cs

Line 602 in 7191cb6

Console.Clear();

This line being optional depending on a setting made in the driver, if possible.

Alternatives Considered

No response

[nickprotop]

Hi @CarrnellTech — happy to add this, and good question. Let me clear up the Direct vs Buffer thing first since it's related, then ask what you're after.

Direct vs Buffer (you were close!):

• Buffer = the library draws the whole screen into memory first, then sends only what changed. Smooth, no flicker. (This is the default and what you want.)
• Direct = it writes straight to the terminal as it goes. Simpler, but it flickers and is slower.

They look the same to you because the visible result is identical — the difference is only in how it's drawn. So that part is working as intended; nothing's wrong on your end.

About the clear-on-exit: what happens on exit actually depends on your OS, so two quick questions:

1. What OS / terminal are you on? (Linux, macOS, Windows? WSL?)
2. What do you want to see after the app exits — pick whichever fits:
   • (A) Your terminal exactly as it was before you launched the app (your old prompt/history back).
   • (B) The app's last screen left frozen in place (so the final UI stays visible).

The reason I ask: on Linux/macOS the app runs on a separate "screen layer," so when it exits we can bring your original terminal back untouched (option A) — that's easy and is probably what you want. On Windows there's no separate layer, so the app draws right over your terminal; we can't bring the original back, but we can stop wiping the screen so the app's last frame stays (option B).

So tell me your OS + whether you want A or B, and I'll wire up exactly that. 👍