Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows 11- issue (with console) #2251

Open
ttool22 opened this issue Dec 12, 2022 · 4 comments
Open

Windows 11- issue (with console) #2251

ttool22 opened this issue Dec 12, 2022 · 4 comments
Labels

Comments

@ttool22
Copy link

ttool22 commented Dec 12, 2022

Wundows 11 update
A clear and concise description of what the bug is.
image

@BDisp
Copy link
Collaborator

BDisp commented Dec 12, 2022

Please, indicate what driver and what console do you are using. What do you are running? Something from the UICatalog or your own code? If is your code can you share, please.

@tig tig added the bug label Dec 12, 2022
@markjamesm
Copy link

markjamesm commented Feb 9, 2023

This is also happening to me on Windows 11.

Steps to Reproduce

Build my program in VS 2022 in either debug or release mode, the window looks normal:

dioscuri-normal

Next, resize the terminal window (my program will resize responsively), but then close it at a different size than what you started with. Afterwards, build the project again and the window looks like this:

term-output-resized

The issue persists until I relaunch Visual Studio. My codebase is here:

https://github.com/Small-NET/Dioscuri

@BDisp
Copy link
Collaborator

BDisp commented Feb 9, 2023

Sorry but I can't reproduce this with the information you provided and with your codebase . The only issue I seen is the app crash if we resize the the height to zero, but this was already fixed in PR #2268 and #2294. If this still happens, please let me know, by providing a .gif file of all the steps. You can try to add the Terminal.Gui project instead of the nuget package to only check if this issue still happens.

@tig
Copy link
Collaborator

tig commented Feb 10, 2023

I see what the OP is seeing here occastionally when running Terminal.Gui apps in the VS debugger. When the app initially loads, the screen is corrupted as descirbed. Resizing the console usually (but not always!) fixes it.

Closing the console created by the debugger and re-running the app usually fixes it.

I have not dug into it because i sorta assumed it was a Windows Terminal bug. I am not sure though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

4 participants