Fix incorrect string parameters for dispatch schedule assigned to depot
See: #368
This commit is contained in:
@@ -7185,7 +7185,7 @@ STR_SCHDISPATCH_SUMMARY_NOT_ENABLED :{BLACK}This sch
|
||||
STR_SCHDISPATCH_SLOT_OUTSIDE_SCHEDULE :{BLACK}One or more departure slots are outside the schedule duration.
|
||||
|
||||
STR_SCHDISPATCH_NOT_ASSIGNED_TO_ORDER :{BLACK}This dispatch schedule is not assigned to an order.
|
||||
STR_SCHDISPATCH_ASSIGNED_TO_ORDER :{BLACK}This dispatch schedule is assigned to order {NUM}: {STRING1}.
|
||||
STR_SCHDISPATCH_ASSIGNED_TO_ORDER :{BLACK}This dispatch schedule is assigned to order {NUM}: {STRING2}.
|
||||
|
||||
STR_SCHDISPATCH_ADD_DEPARTURE_SLOTS_START :{BLACK}Start:
|
||||
STR_SCHDISPATCH_ADD_DEPARTURE_SLOTS_STEP :{BLACK}Period:
|
||||
|
@@ -520,7 +520,8 @@ struct SchdispatchWindow : GeneralVehicleWindow {
|
||||
|
||||
case OT_GOTO_DEPOT:
|
||||
SetDParam(1, STR_DEPOT_NAME);
|
||||
SetDParam(2, order->GetDestination());
|
||||
SetDParam(2, v->type);
|
||||
SetDParam(3, order->GetDestination());
|
||||
break;
|
||||
|
||||
default:
|
||||
|
Reference in New Issue
Block a user