"script-include-table" container
From TrainzOnline
(Difference between revisions)
(Created page with "The "script-include-table" container is a top-level config.txt file entry available to any Asset which derives from KIND TrainzBaseSpec (in short, all Assets.) Thi...") |
m (Added example and added category sortkey) |
||
| Line 11: | Line 11: | ||
It is typically best to restrict such references to [[KIND Library]] assets, however this is not mandatory and any assets can be referenced. | It is typically best to restrict such references to [[KIND Library]] assets, however this is not mandatory and any assets can be referenced. | ||
| + | ==Example== | ||
| + | script-include-table { | ||
| + | a-key <kuid:nnnn:nnnnn> | ||
| + | } | ||
| − | [[Category:Config Container]] | + | |
| + | [[Category:Config Container|S]] | ||
Latest revision as of 15:59, 22 January 2014
The "script-include-table" container is a top-level config.txt file entry available to any Asset which derives from KIND TrainzBaseSpec (in short, all Assets.) This container allows the asset to directly include another asset's scripts from the parent asset's script file(s).
The extensions container is a list of custom tags or subcontainers with a specific naming convention.
[edit] Supported Tags
This container is a simple key-value table of scripted assets which are searched for script includes when compiling the asset's script file(s). The key is currently unused; the value indicates the KUID of the asset to include.
[edit] Validation
It is typically best to restrict such references to KIND Library assets, however this is not mandatory and any assets can be referenced.
[edit] Example
script-include-table {
a-key <kuid:nnnn:nnnnn>
}
