User experience improvement - simplicity
1. Naming
Lets name the feature
Departure queue manager abreviation used in the fallowing text is DQM
Because:
- it better describe what it does. Manages a queue of trains which are heading to a destination.
- there is an proposal to set balanced OR nearest dispatching. Therefore is better to use words as
manage not
limit
- wording "
stop limit" sounds restrictively and negative. This feature helps & improve not restrict.
2. On / Off status & values
Current proposal is to enable feature first, then set its value. It means two controls. What happen when you enable the feature and set value to zero? Make it rather one control option.
Lets make Departure max queue lenght initial value = 0
Then user can rise it up.
That means, feature is always there.
initial value is current status, queue of zero lenght. Then any non zero value means Departure queue manager is working.
It is the same behavior of logic as for combinator variables.
So the description would be:
Enable trains limit >>> Departure queue manager : Max queue lenght
Set trains limit >>> Set Max queue
Read trains counts >>> Read Current queue
Input signal >>> Departure queue manager
Trains limit >>> Max queue lenght
Output signal >>> Departure queue manager
Trains count >>> Current queue lenght
Enable/disable check box for "Enable Trains limit" is not needed. (value zero does it)
3. Nearest OR Balanced dispatching option
There is nice improvement proposal to the feature. Allow user tweak dispatch destination.
When
DQM is > 0 then radio switch is available to choose Balanced OR nearest dispatching
The Departure queue manager choose the destination station depends on different criteria:
a] Nearest - current logic - initial value - value zero
b] Balanced - it dispatches a train to the station which has value Current queue lenght lowest - value one (for combinator read/set)