IS:size objectVis: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
(added the semantics for the width and height) |
(added notes) |
||
Line 12: | Line 12: | ||
*{{attr|width}}: {{xsdType|double}}; required | *{{attr|width}}: {{xsdType|double}}; required | ||
*{{attr|height}}: {{xsdType|double}}; required | *{{attr|height}}: {{xsdType|double}}; required | ||
|notes= | |||
Though one can define a "size" for a platform they should not do it because they are <trackElementVis> elements. This implies that there is some "default" value for the railway platforms and other track elements somewhere in the software. | |||
}} | }} |
Latest revision as of 13:09, 20 April 2023
<size>
|
Scheme description / Schemenbeschreibung
Position of <size> in the XML-Tree / Position von <size> im XML-Baum
- Parent: <objectVis>
- Children: None
Multiplicity / Anzahl
Semantics / Bedeutung
Size of the OCP/object visualization element. Replaces and generalizes <ocpVis>.(introduced with version 2.5)
Attributes of <size> / Attribute von <size>
- width: Defines the width of the OCP/object visualization element.
- height: Defines the height of the OCP/object visualization element.
Syntactic Constraints / Syntaktische Beschränkungen
Best practice & Examples / Empfohlene Anwendung & Beispiele
Not yet described. / Noch nicht beschrieben.
Notes / Anmerkungen
Though one can define a "size" for a platform they should not do it because they are <trackElementVis> elements. This implies that there is some "default" value for the railway platforms and other track elements somewhere in the software.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.