Skip to content

Reduce minimum width of map window#3191

Closed
LeeSpork wants to merge 1 commit intoOpenLoco:masterfrom
LeeSpork:thin-map-window
Closed

Reduce minimum width of map window#3191
LeeSpork wants to merge 1 commit intoOpenLoco:masterfrom
LeeSpork:thin-map-window

Conversation

@LeeSpork
Copy link
Copy Markdown
Contributor

@LeeSpork LeeSpork commented Aug 6, 2025

It feels bad when you're resizing a window and you hit against its minimum width way before you expect to. The minimum width of the map window felt just a bit too wide to me, when playing at a small resolution - a very mild inconvenience.

Reduced it from 350 to 161 (chosen to nicely frame the max number of tabs it has). Now the map can be resized to be too small to be useful, which I think is better.

Before/after:
image

@AaronVanGeffen
Copy link
Copy Markdown
Member

AaronVanGeffen commented Aug 6, 2025

Now the map can be resized to be too small to be useful, which I think is better.

I honestly don't understand why this is desirable, to be honest. If anything, we should increase the minimum window size, imo. Could you elaborate?

@LeeSpork
Copy link
Copy Markdown
Contributor Author

LeeSpork commented Aug 7, 2025

I honestly don't understand why this is desirable, to be honest. If anything, we should increase the minimum window size, imo. Could you elaborate?

My philosophy here: more user choice/freedom = more fun/better. If the player wants the minimap to be smaller than we would assume to be practical, why stop them? It doesn't seem to be breaking anything (other than the scrollbar thumbs, but that's a separate issue)

@LeftofZen
Copy link
Copy Markdown
Contributor

LeftofZen commented Aug 7, 2025

I was curious what other programs do in this regard:

Chrome:
image

Visual Studio:
image

Paint:
image

Notepad:
image

Chrome and VS both let the user resize the window to a completely unusable size, whilst Paint and Notepad limit the min size to keep them technically usable.

@LeftofZen
Copy link
Copy Markdown
Contributor

LeftofZen commented Aug 8, 2025

I had a think about this.

If the player wants the minimap to be smaller than we would assume to be practical, why stop them?

Because...its not practical. Is a mechanic going to install 6 inch wheels on your car? Even if it's technically possible, they aren't going to do that simply because it doesn't make sense to do so. In other words, Chrome and VS are bad, Notepad and Paint are good.

Objectively, in UI/UX design, the minimum window size is not a user-configurable property. This is because it is the designer's job to ensure the window layout doesn't break at small sizes, to ensure UI elements don't overlap or get hidden, text doesn't get resized or hidden, and to generally provide a usable and useful user experience. In other words, a window that is too small to be usable does not provide a valid and good UX. If a designer cannot control minimum (and maximum) window sizes, the they cannot hope to create a good UX.

I would argue the current minimum width is fine, and the minimum height needs to be increased so that the minimap is roughly a square at its minimum window size.

@LeeSpork
Copy link
Copy Markdown
Contributor Author

LeeSpork commented Aug 8, 2025

the minimum window size is not a user-configurable property.

Yes, and I did my due diligence to ensure that the minimum I set does not break the layout or hide any widgets (barring the existing scrollview bug) unlike your Chrome and VS examples.

Though I will concede that this is totally overkill, as is the existing minimum height, and is an entirely unnecessary change.

*(Well, assuming the title text isn't substantially longer in any translations).

@LeeSpork
Copy link
Copy Markdown
Contributor Author

LeeSpork commented Aug 8, 2025

Well, I did forget about the status text at the bottom, when hovering over an industry type.
image
(But it is still handed cleanly with ellipses, and the user can still expand the window again if they desire to read the rest of it.)

@AaronVanGeffen
Copy link
Copy Markdown
Member

Closed in favour of #3193.

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

Successfully merging this pull request may close these issues.

3 participants