• While this is vanilla behaviour, the text columns rendered over the vehicle list makes them hard to read. Perhaps make the text columns have a translucent background? (is that even possible in loco?). If there is no better solution, happy to leave this for now as it is vanilla behaviour.

Looking at the screenshot I would like to propose to make the rows taller to visually separating the text and the image. But that should IMHO be the subject of another PR.

Thanks for giving this a go, @LeftofZen! Appreciate the feedback.

The dropdowns at the bottom of the window are too big/the area they're in is too small; they;re over the window border

This is a good point. I haven't changed anything here, but this seems to be a mistake from when I introduced these dropdowns in the first place. I think we can spare a few more pixels 😄

Resizing the window smaller makes the dropdowns at the bottom disappear

This is deliberate, so the dropdowns don't overlap with the status line. I can tweak cut-off point a little more, though.

Resizing the window smaller makes the grid columns disappear (instead of resizing smaller to fit them on

This is true, but vanilla behaviour. Widening the window only increases the size of the name column. Shrinking the columns is a bit difficult tbh, as the texts don't have good breaking points for auto-ellipsism.

It seems there is a max size with the vehicle window (there was no max size with the object selection window)

Yes, all windows have a max size. The object selection window has 2000x2000, while this one has 1200x1200. I chose to go with smaller dimensions due to the 'auto resize' feature being enabled for this one. (Click resize handle to maximise.) Thinking on it some more, though, I think we can increase the vertical limit with no issues, though, so I'll amend that.

While this is vanilla behaviour, the text columns rendered over the vehicle list makes them hard to read. Perhaps make the text columns have a translucent background? (is that even possible in loco?). If there is no better solution, happy to leave this for now as it is vanilla behaviour.

This doesn't sound like something we can do easily, but I'm open to suggestions. Perhaps you could file an issue with a mockup proposal? It's a bit out of scope for this PR, imo.