Track Section Names: Difference between revisions

From Planimate Knowledge Base
Jump to navigation Jump to search
m (1 revision(s))
No edit summary
Line 1: Line 1:
<font face="Arial">Sections in a track network have an internal identifying name. However in a number of instances, they are identified by the two objects they connect between.
Sections in a track network have an internal identifying name. However in a number of instances, they are identified by the two objects they connect between.




A button "Update Names" in the Section Details dialog automatically sets the "internal" name of each section of track to one derived from its two end points. This assists in debugging where sections are identified by the internal name, not the full name generated from their two end points which is used in other dialogs.
A button "Update Names" in the Section Details dialog automatically sets the "internal" name of each section of track to one derived from its two end points. This assists in debugging where sections are identified by the internal name, not the full name generated from their two end points which is used in other dialogs.
</font>
----
----
[[Category:Lookahead]]
[[Category:Lookahead]]
[[Category:Spatial Network]]
[[Category:Spatial Network]]
[[Category:Track/Section]]
[[Category:Track/Section]]
[[Category:Release Note]]
<font size="2">idkbase note 142</font>
<font size="2">idkbase note 142</font>

Revision as of 17:18, 10 January 2008

Sections in a track network have an internal identifying name. However in a number of instances, they are identified by the two objects they connect between.


A button "Update Names" in the Section Details dialog automatically sets the "internal" name of each section of track to one derived from its two end points. This assists in debugging where sections are identified by the internal name, not the full name generated from their two end points which is used in other dialogs.


idkbase note 142