MetaTable: Difference between revisions

From SignalWiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
 
(10 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{DeveloperNav}}
The MetaTable defines the author, date, and version number of a timetable. This allows database developers to define information that uniquely identifies the database. This helps the simulator to keep track of which saved simulation uses which database. The fields are as follows:
The MetaTable defines the author, date, and version number of a timetable. This allows database developers to define information that uniquely identifies the database. This helps the simulator to keep track of which saved simulation uses which database. The fields are as follows:


Field: AUTHOR  
;AUTHOR
Type: string  
:(string)
Purpose: Database developer's name.
:Database developer's name.
 
;DATECREATED 
:(date)
:Defines the most recent date the database was edited or otherwise changed.


Field: DATECREATED 
;VERSION
Type: date   
:(string)
Purpose: Defines the most recent date the database was edited or otherwise changed.
:Uniquely identifies the database. Prevents a saved simulation from using the wrong database. Value is a [http://en.wikipedia.org/wiki/Globally_unique_identifier GUID]. After editing a timetable, this value should be changed. Values may be generated in a variety of ways; one useful way is to visit [http://createguid.com/ createguid.com].


Field: VERSION
;COMMENTS
Type: string
:(string)
Purpose: Uniquely identifies the database. Prevents a saved simulation from using the wrong database. Value is a [http://en.wikipedia.org/wiki/Globally_unique_identifier GUID].
:This field can be left empty.


Field: COMMENTS
{{DeveloperNavBottom}}
Type: string
Purpose: This field can be left empty.

Latest revision as of 12:04, 13 July 2011

Contents | Developers pages | Command Line Options | Timetables | Scenario Creation | Developing Installers



The MetaTable defines the author, date, and version number of a timetable. This allows database developers to define information that uniquely identifies the database. This helps the simulator to keep track of which saved simulation uses which database. The fields are as follows:

AUTHOR
(string)
Database developer's name.
DATECREATED
(date)
Defines the most recent date the database was edited or otherwise changed.
VERSION
(string)
Uniquely identifies the database. Prevents a saved simulation from using the wrong database. Value is a GUID. After editing a timetable, this value should be changed. Values may be generated in a variety of ways; one useful way is to visit createguid.com.
COMMENTS
(string)
This field can be left empty.

Contents | Developers pages | Command Line Options | Timetables | Scenario Creation | Developing Installers