space usage of Red Build/Order Menu

[knorke]

There are some cases where the menu adds a second page.
For example for the commanders all buildoptions and commands are on page 1 - except "capture" which is alone on page 2.
If they were no flip-page arrows, in this case everything would fit onto the same page.

Similiar:
T2 con vehicle has T2 vehicle lab as only option on page 2
T2 conbot has Juno and Shipyard on page 2. (and compared to commander, two empty rows at top because attack, Dgun etc are missing. So extra wastefull)
etc

Also widgets to hide some command buttons (stop, move, fight,..all the ones not even a newbie clicks) do not work with Red Menu.

tl;dr:
Do not add second page if there will be only one extra row on it.
Make option to hide useless buttons.
With that, in most cases everything will fit onto one page.

[Silentwings]

You are right, its on the list of things to do now: http://imolarpg.dyndns.org/trac/balatest/ticket/334.

[Jools]

There is alredy a widget for that: for hiding useless buttons.

[Silentwings]

That widget is for buttons which give commands - knorke (I think) means the buttons that are build icons.

[Jools]

Yes, but capture is an order button.

[Silentwings]

The widget only hides buttons and it does hide buttons that some people use (I thought about adding it once and went around asking). In any case I think thats best done by unitdefs.

But the point here is that the widget doesn't remove the arrows in the case when removing the menu pages arrows would give you an extra row of icons and mean that everything could fit on a single plage.

[Jools]

Yeah, I see. Then best IMO would be to refine red build menu to do that. Can't you just count the no of cmddescriptions and based on that choose to show/hide arrows?

[Silentwings]

Yes!