Consolidated station information?

[wlindley]

Thanks to all for the excellent recent improvements.  (Not sure whether how or whether this might pertain to Standard so, moderators, feel free to move the topic.)
With the additional information in the Details box, and the rearrangement of the tabs in the ordinary station box, do we in fact need the "Details" button and a separate dialogue?  Or could the little extra header information there, and the tabs in it, be placed in the ordinary (and then single) station information dialogue, perhaps as shown?  (Transferred header sections circled)  Thoughts / preferences, anyone?

[Matthew]

I have been thinking exactly the same thing all week. I would strongly support this, provided that the window is still slim enough to fit in our players' display width. A very high proportion of my visits to stations are to use the 'Services' tab and the 'Details' button is just an extra click.

[Mariculous]

The number of lines per waytype and company feature is a display I'd prefer in the "normal" window anyways.
I totally support this.

[zook2]

Ditto here.

One other thing: it's the same issue with the convoy window. Many unnecessary clicks. If the details button were to disappear, could we have the Withdraw, Retire, Sell buttons there? Perhaps just (W) (R) (S) buttons with a tooltip. Move to Depot could be grouped with those, too.

[Mariculous]

If the details button were to disappear, could we have the Withdraw, Retire, Sell buttons there?

Imho, such tabbed windows should remember the last used tab and open up new windows of the same type with that tab selected.
That will save a lot of clicks in many cases.
Picking up the Witdraw/retire/sell example, instead of four clicks: "mainWindow -> detailsWindow -> maintenanceTab -> retireButton", there will only be two: "mainWindow -> retireButton" in case of mass retirement.

[wlindley]

I have been studying halt_info and halt_detail (.h, .cc) and while there is some overlap, it is as you say far from simple.

The detail window has a listener so the line list can update whenever the current-player changes, for example.  Mostly I wonder whether it is possible to clean up the design of the code to make UI changes more obvious how to create?