Common script for signal types
This blueprint proposes to introduce an additional variable to the signal type definition in the sigcfg.dat file which allows the use of common signal scripts for different signal types.
Presently, each signal type must have its own script, using the name of the signal type as identification for the script. However, there are often different signal types which have common processing, the difference being the location of the lights etc., or the type of information which is shown (e.g. sets of theatre boxes showing different characters).
As each signal type must have its own related script means that there are just multiple scripts which are completely the same - or should be, but typing errors or updates which are not properly applied to all related scripts can create differences and thus cause errors. The requirement to have multiple similar scripts simply is a nuisance.
Using the proposed new variable will link a signal type to the identified script. This may be a script defined for another signal type, or it may be a general defined script using a separate name.
The syntax of the variable is :
or_script <scriptname>
Discussion: http://
Roadmap: https:/
Blueprint information
- Status:
- Complete
- Approver:
- James Ross
- Priority:
- Medium
- Drafter:
- r.roeterdink
- Direction:
- Approved
- Assignee:
- r.roeterdink
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- 1.3
- Started by
- r.roeterdink
- Completed by
- James Ross
Related branches
Related bugs
Sprints
Whiteboard
Implemented in X3863.