-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Display a dialog when the user selects an invalid font #1017
Comments
I also see an earlier report (#550) that Terminal would actually crash when a profile referred to a nonexistent font name. Is that not happening anymore? Perhaps that problem was partially fixed, resulting in what you see. |
I haven't had it crash on me yet when I change the font to an invalid one. It just makes the font extremely small. |
I mean, literally anyone who isn't me can go F5 the thing in Visual Studio setting a breakpoint in But if no one else does that, I'll get to this eventually. |
Well, for what it's worth, I can't reproduce this problem. I gave a profile a nonexistent font name and Terminal crashed as per #550 when creating a tab with that profile; it didn't show a tab with tiny text as you report here. |
@metathinker this occurred when I had a terminal tab already open when I was editing the profile. @zadjii-msft are you at least informing the user why the terminal crashed? |
@matt2405warner considering the terminal was hard crashing, I don't think the app had a chance to catch the exception that triggered the crash. Now that #903 is complete, we certainly can add another message here |
I've tried changing to a non-existent font today, and it hard-crashes the entire application when I do. |
@kmoberg, I fixed #550 19 hours ago. It'll be in the next release or you can build from master to get the fix. However, the way I fixed it just resulted in the DX renderer trying things until it can find a font. If we're to add a dialog too, we probably need to detect that the requested font doesn't match the returned font and display. I can take the issue from here. |
How do you find the string that represents the font variant you want? |
Display a warning message when the DirectX renderer resolves a font that isn't the one you selected to warn that it couldn't be found. Also I wrote the dialog event chain out of `TermControl` to be reusable in the future for other messages the control might want to tell a host about and various levels. ## Validation Steps Performed - Manual validation, setting bad font name, fixing font name with `settings.json`. Closes #1017
🎉This issue was addressed in #8207, which has now been successfully released as Handy links: |
Summary of the new feature/enhancement
Currently when changing the 'fontFace' to a font that doesn't exist the font size just gets so small (~0.5 font size) that you can't read the text.
Proposed technical implementation details (optional)
It would be nice if the terminal informed the user that the font is not valid - Maybe a pop-up/modal?
The text was updated successfully, but these errors were encountered: