From: Kevin D. <kev...@us...> - 2011-05-18 15:40:37
|
Update of /cvsroot/jmri/help/en/html/tools/signaling In directory vz-cvs-3.sog:/tmp/cvs-serv14035 Modified Files: DefineNewAspects.shtml Log Message: Updated to follow changes in signalmast specific aspects Index: DefineNewAspects.shtml =================================================================== RCS file: /cvsroot/jmri/help/en/html/tools/signaling/DefineNewAspects.shtml,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** DefineNewAspects.shtml 8 Apr 2011 16:43:58 -0000 1.4 --- DefineNewAspects.shtml 18 May 2011 15:40:34 -0000 1.5 *************** *** 93,96 **** --- 93,98 ---- <comment></comment> <imagelink></imagelink> + <speed></speed> + <diverging></diverging> </aspect> </pre></code> *************** *** 108,111 **** --- 110,125 ---- more work. <p> + The speed element, if present, should either be a numerical value or a string + value that has been defined int eh signalSpeeds.xml file. The speed element + relates to the maximum speed a train can pass the aspect at. The signalmast logic + uses this speed to help determine which aspect should be displayed where there + are multiple possible aspects. + <p> + The diverging element, if present, should simple be entered in as a 'yes'. + The diverging element indicates that this specific aspect is used when a + turnout has been thrown in the path ahead. The signalmast logic uses this element + to help determine which aspect should be displayed where there are multiple + possible aspects. + <p> Below the aspect blocks, there's a block that names all the valid appearance files, e.g.: *************** *** 136,140 **** <code><pre> ! <appearance> <aspectname>Clear</aspectname> <show>green</show> --- 150,154 ---- <code><pre> ! <appearance><br> <aspectname>Clear</aspectname> <show>green</show> *************** *** 142,146 **** <reference></reference> <imagelink></imagelink> ! </appearance> </pre></code> --- 156,160 ---- <reference></reference> <imagelink></imagelink> ! </appearance><br> </pre></code> *************** *** 163,174 **** As the appearance names are all user defined and can be in any language, it is necessary to identify some specifically used aspects that various ! parts of JMRI will specifically ask for. This information can be entered at after the appearance information in the following form. <code><pre> <specificappearances> ! <danger>Danger</danger> ! <permissive>Off</permissive> ! <held>Danger</held> ! <dark>Not lit</dark> </specificappearances> </pre></code> --- 177,200 ---- As the appearance names are all user defined and can be in any language, it is necessary to identify some specifically used aspects that various ! parts of JMRI will specifically ask for.<br> ! Each specific aspect can be given an alternative image to use other than that given ! in the main appearance definition.<br> This information can be entered at after the appearance information in the following form. <code><pre> <specificappearances> ! <danger> ! <aspect>Danger</aspect> ! </danger> ! <permissive> ! <aspect>Off</aspect> ! </permissive> ! <held> ! <aspect>Danger</aspect> ! <imagelink>held.gif</imagelink< ! </held> ! <dark> ! <aspect>Not Lit</aspect> ! <imagelink>notlit.gif</imagelink< ! </dark> </specificappearances> </pre></code> *************** *** 181,191 **** The purpose of the map is to define which potential appearances are valid depending upon what appearance is being displayed on the signal mast that is ahead of us. ! This mapping can be a simple one-to-one, E.g. Advanced signal mast is showing Danger, we should show Caution. Or a more complex one-to-many map where there could be multiple appearances that we could display, ! E.g. Advanced signal is showing Approach, but we could display either a ! Clear or Diverging Clear depending upon other conditions. <p> All of the mappings, are contained within the <aspectMappings> tags, within their own <aspectMapping> tag ! <h3>Check Your Work</h3> --- 207,234 ---- The purpose of the map is to define which potential appearances are valid depending upon what appearance is being displayed on the signal mast that is ahead of us. ! This mapping can be a simple one-to-one, E.g. Advanced signal mast is showing Approach, we should show Clear. Or a more complex one-to-many map where there could be multiple appearances that we could display, ! E.g. Advanced signal is showing Stop, but we could display either a ! Approach or Diverging Approach depending upon other conditions. ! <p> ! The value of the Advanced Aspect can be any that is defined in the Aspect table ! for that signalling system.<br> ! The value of Our Aspect, must be one that is defined and supported by the ! defined in the appearance file. <p> All of the mappings, are contained within the <aspectMappings> tags, within their own <aspectMapping> tag ! <code><pre> ! <aspectMappings> ! <aspectMapping> ! <advancedAspect>Approach</advancedAspect> ! <ourAspect>Clear</ourAspect> ! </aspectMapping> ! <aspectMapping> ! <advancedAspect>Stop</advancedAspect> ! <ourAspect>Approach</ourAspect> ! <ourAspect>Diverging Approach</ourAspect> ! </aspectMapping> ! </aspectMappings> ! </pre></code> <h3>Check Your Work</h3> |