The building blocks of your Generic Application.
LibraryManager creates and edits the object library that TrackPlanner CAD loads at start-up: the object types, their symbols and their attributes. It is where a signalling practice is encoded once and reused on every station drawn to it, without a line of code changing.
THE OBJECT LIBRARY
What the library holds.
When TrackPlanner CAD starts, it loads the object library configuration file and learns the object shapes and names, and the attribute names and value types. Everything the design office sees afterwards comes from that file.
Which means the file is the standard. Encode it once, and every station drawn afterwards is drawn to it.
- Railway objects with properties, attributes and graphical representation
- Symbol shapes drawn in the tool itself
- Railway sections (track sections, axle counters)
- Path types with overlaps, flanks and additional properties
- Areas and zones, such as emergency and shunting areas, with colours
- Cabinets and relays down to racks, boards and pins
- Name generators and the rules that identify routes
- Attribute categories and Enum types Visualisation layers, palettes and rail styles
- Name translations across languages
THE MINIMUM
Two roles, and everything else is yours.
A library is valid for TrackPlanner CAD as soon as it defines RailPoint and RailEnd. Everything above that is the customer’s own signalling practice.
Why this matters commercially
A tool that has to be modified for each national market is a project. A tool whose behaviour is configured in a file the customer owns is a product. This page is where that difference is made visible.
A tool that has to be modified for each national market is a project. A tool whose behaviour is configured in a file the customer owns is a product. This page is where that difference is made visible.
