[Jmri-commits] help/en/package/jmri/jmrit/beantable LRouteAddEdit.shtml, 1.2, 1.3

[Pete C. <pet...@us...>]

Update of /cvsroot/jmri/help/en/package/jmri/jmrit/beantable
In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv24682

Modified Files:
	LRouteAddEdit.shtml 
Log Message:
Clarify explanation (hopefully)

Index: LRouteAddEdit.shtml
===================================================================
RCS file: /cvsroot/jmri/help/en/package/jmri/jmrit/beantable/LRouteAddEdit.shtml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** LRouteAddEdit.shtml	15 Apr 2009 01:21:47 -0000	1.2
--- LRouteAddEdit.shtml	22 Apr 2009 06:36:56 -0000	1.3
***************
*** 75,79 ****
  State</b> column.</p>
  
! <p>Devices selected with "non-veto" states are grouped as an "OR" clause.  Devices
  selected with a "veto" state are grouped as an "AND" clause.  That is, when any 
  "non-veto" state becomes true, the l-route is able to trigger.  However, if any of the
--- 75,79 ----
  State</b> column.</p>
  
! <p>Devices selected with "non-veto" states are grouped as an "OR" clause.  Triggers
  selected with a "veto" state are grouped as an "AND" clause.  That is, when any 
  "non-veto" state becomes true, the l-route is able to trigger.  However, if any of the
***************
*** 81,97 ****
  
  <p>On Tab 1, the Logix Route Type <b>New</b> will put the above logic into a single
! Logix Conditional.  If the <b>Old</b> option is selected, each devices with a
  "non-veto" state is put into a separate Conditional.  The behavior for this
  option is the 
  l-route will trigger whenever one of these device states becomes true - even when
! the logical expression as a whole is already true.   The other difference with the
! <b>Old</b> option is that the "veto" variables are not enabled for triggering. 
  In summary, the <b>Old</b> option emulates a standard Route and the <b>New</b> 
! option is a standard Logix Conditional.  Variations on these behaviors can be 
! tuned with further editing in the Logix Table.
  
! <p>Also note that control variables selected with "On Change" states need a separate
  Logix Conditional in order for the l-route actions to trigger on every change of state
! of these variables.
  
  <p>The radio buttons allow you to limit the display of devices to only those you
--- 81,100 ----
  
  <p>On Tab 1, the Logix Route Type <b>New</b> will put the above logic into a single
! Logix Conditional.  If the <b>Old</b> option is selected, each trigger with a
  "non-veto" state is put into a separate Conditional.  The behavior for this
  option is the 
  l-route will trigger whenever one of these device states becomes true - even when
! the logical expression as a whole is already true. (i.e. the action is repeated, even
! another trigger has already caused the action to complete.)   The other difference is when
! the <b>Old</b> option is specified, the "veto" variables are not enabled for triggering.
! This means the actions are not triggered when the vetoes are removed.  Use the <b>new</b>
! option if you want actions to be triggered when the vetoes are removed.  
  In summary, the <b>Old</b> option emulates a standard Route and the <b>New</b> 
! option has the behavior of a standard Logix Conditional.  Variations on these behaviors  
! can be tuned with further editing in the Logix Table.
  
! <p>Note that control variables selected with "On Change" states need a separate
  Logix Conditional in order for the l-route actions to trigger on every change of state
! of these variables.  
  
  <p>The radio buttons allow you to limit the display of devices to only those you