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

[Bug]: Error messages are bigger as of the recent UI changes #10174

Closed
James103 opened this issue Nov 14, 2022 · 4 comments
Closed

[Bug]: Error messages are bigger as of the recent UI changes #10174

James103 opened this issue Nov 14, 2022 · 4 comments

Comments

@James103
Copy link
Contributor

James103 commented Nov 14, 2022

Version of OpenTTD

cbb2d53 on Windows 10, 64-bit

Expected result

Error messages should be about the same size as before the recent UI changes / release 12.2 and older.

One line:
image

Two lines:
image

Actual result

Error messages are significantly bigger (wider and taller) compared to 12.2 and older.
This happens even on 1x interface scaling which all screenshots were taken at.

One line:
image

Two lines:
image

Steps to reproduce

  1. Start OpenTTD.
  2. Trigger any error message.
  3. Notice the message is significantly bigger compared to in older releases.
@PeterN
Copy link
Member

PeterN commented Nov 14, 2022

Bug, or feature?

@ldpl
Copy link
Contributor

ldpl commented Nov 15, 2022

Vertical feature horizontal bug xD

@PeterN
Copy link
Member

PeterN commented Nov 15, 2022

If you want to play with and suggest a better size, it's the new modalpopup dimension, defined in widget.cpp:152.

Edit: This dimension is used by ErrmsgWindow, QueryWindow, and any of the progress-bar windows.

Might be sufficient to use the frametext dimension on ErrmsgWindow instead, to leave the rest as is.

@2TallTyler
Copy link
Member

I'd expect a two-line message to be taller than a one-line message, and the old message appears to have been lacking proper text padding.

Not a bug, although PRs are open if somebody wants to resize it. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants