Bug 5963: Rpl Series Slot: Sync Range with Run Period: Option to include Init Timestep
Bug Number: 5963
Release notes (y/n): Yes
For Release Nums: 7.1 (maybe 7.0.8)

When Series Slots with (RPL) Expressions are set to "Always Sync Range with 
Run Period", there is an option to include the Initial Timestep (i.e. one 
timestep before the Run Start date). 

QtUtils/RunParamFrame is a panel used in several dialogs.  The relevant 
use for this change is in Q3GUI/SlotTimeseriesRangeQtDlg dialog.  The 
RunParamFrame constructor now has an option SeriesSlot* parameter. If a 
call to SeriesSlot:: usesIncludeInitialTimestepInRunPeriod() is true on 
that instance, the panel shows a new [X] "Include Initial Timestep in Run 
Period" checkbox.  See this screenshot:

   http://cadswes2.colorado.edu/~philw/2017/bugs/5963/NewCheck1.png

That checkbox edits the _includeInitialTimestepInRunPeriod on that slot 
(the setting of that field is effected actually in the panel's client, 
SlotTimeseriesRangeQtDlg).  The state of that new checkbox also conditions 
the displayed "Begin" time Date/Time Spinner when the "Always Sync Range 
with Run Period" is checked AND when the "Sync With Run Period" button is 
clicked.

Series Slot, new fields:

   // Computed time range support [Gnats 5963]
   bool _includeInitialTimestepInRunPeriod;

   bool usesIncludeInitialTimestepInRunPeriod() const;
      ... currently true only for SeriesSlots which are 'computedByExpr()'.
   bool includeInitialTimestepInRunPeriod() const;
   void setIncludeInitialTimestepInRunPeriod (bool);

SERIALIZATION (tcl):
  "$s" syncWithRun-InclInitTstepInRunPeriod 1

---