Object Property Attributes of Tracks

From Planimate Knowledge Base
Revision as of 11:38, 9 May 2011 by Rick (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Track Object Properties

A number of Object Properties are particular to Track Objects. The following Track Object Properties can be accessed using Routines:

ObjectTrackStart

This is a read-only property that gives you the index from the _ModelObjects Listing that corresponds to the Portal at which the Track Object Starts. Knowing this, you can determine which direction on the Track Object is ‘Forward”.

ObjectTrackEnd

This is a read-only property that gives you the index from the _ModelObjects Listing that corresponds to the Portal at which the Track Object Ends. Knowing this, you can determine which direction on the Track Object is ‘Forward”, or perhaps, then send information or events to this portal which will change the train item.

ObjectTrackTableRow

This is a read-only property that gives you the row index from the table being referenced for Track Network Details pertinent to the (Track Object _ModelObjects list) index specified in the attribute reference.

This information provides you with the row address for the Track Object, with which you can make changes to the properties of that section contained in the table. It enables rapid lookup of a given section's details without having to search the section table for the row for that section.

SectionFillEnable

A modeller can use this to instruct Planimate on whether a given section is "explorable" when Planimate does a "fill route steps" routine operation to resolve the exact route a train will take.
This is useful where there are optional track configurations being explored, since the tracks for all the variations need to exist. The multiple tracks would normally create ambiguity errors.

To use this property:

  • The "guess intermediate steps" option for the (sparsely defined) route should be off;
  • The modeller should configure the sections using this property then trigger a "FillRouteSteps" for the train, so Planimate can build a non ambiguous route.


This state is not saved as part of the model.
When a model starts/restarts, all sections default to SectionFillEnable=1 (enabled for searching).
The setting of this option only affects the route step filler and has no impact on the train motion logic for existing routes and trains in the network.