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

The problems with the prior implementation of this new feature have been 
addressed.

The "Configure Timeseries" dialog shown for a RPL Expression Series Slot's 
"View" >> "Evaluation Range..." function now presents a new "Include Initial 
Timestep in Run Period" checkbox.  This original mockup image does accurately 
depict the final development:

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

This commit includes these changes:

(1) The "Sync With Run Period" operations no longer "nails" the Series 
Expression Slot's configured TIMESTEP SIZE.  The applied Begin and End 
timesteps are rounded (down and up, respectively) to fall on a time boundary 
for that timestep size.  This had been a problem with the prior commit for 
resolution of problems caused by insufficient (so, buggy) coupling between 
the Q3GUI/SlotTimeseriesRangeQtDlg and QtUtils/RunParamFrame GUI components.

Note: This behavior -- i.e. whether the "Sync With Run Period" functions 
effect the slot's timestep size -- is now controlled by the new parameter to 
this new method:

  void RunParamFrame::syncWithRunInfo (bool rangeOnly);

(2) Fix to other problem reported by David in his 5-25-2017 review:  
The Open Slot dialog's "Evaluation Range" indication now correctly reflects 
whether an active "Always Sync Range with Run Period" starts at the "Run Init"
or "Run Start" timestep.  [See change in Q3GUI/SlotQtDlg.cpp, method: 
SlotQtDlg::updateRplSeriesRange()].

---