-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Initial window height calculation regression #3472
Comments
Are you sure it's a regression? I just tried with 6f36f8b (before the PR was merged) and the size is also incorrect. Before the PR, it was calling BTW here is a TODO for this (it was supposed say "the height of the title bar" for the second option instead of "tab bar" but I thought I had removed this comment so I didn't fix the comment): terminal/src/cascadia/TerminalApp/App.cpp Lines 337 to 342 in 357e835
I didn't fix this bug because it was too hard and (I'm pretty sure, see above) the bug was already there before the PR. Sorry for breaking your PR :( Maybe adding |
For the record, I don't believe this regressed. I thought it was always broken 😝 |
Also, I think this one is probably a /dupe of #2061 |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
Ah ok then, sorry for my accusement. My PR stopped working after I merged with this one because of removed GetDragArea, but I didn't realized it wasn't working with initial sizing before. As to solving this problem, #3182 might help. |
Initial window height is off by titlebar height. This got regressed by #3394 in:
terminal/src/cascadia/WindowsTerminal/AppHost.cpp
Lines 197 to 210 in 357e835
That also blocks #3181 which relys on this size calculation.
Steps to reproduce
fontSize
to 50initialRows
to 2Expected behavior
2 rows should fit in the window
Actual behavior
About 1.5 of a row fits.
cc @greg904.
The text was updated successfully, but these errors were encountered: