RELEASE NOTES - RiverSMART Version 1.10
                           CADSWES - 02/26/2020

___________________________________________________________
SUMMARY OF CHANGES IN RIVERSMART 1.10
-----------------------------
Enhancements
-----------------------------

* The generate scenarios dialog is much improved, with the following
  enhancements:
  o The scenario inputs (hydrologies, demands, etc.) are shown in 
    columns with column headers identifying the inputs.
  o The top level tree items indicate whether there are inactive 
    scenarios, for example:
    > 16 Scenarios will be removed (including 8 inactive Scenarios)
    A checkbox controls whether inactive scenarios are displayed; if 
    they are, they're displayed in "greyed out" text to indicate their 
    status.
  o Highlights indicate why a scenario was added (green background), 
    removed (red background) or invalidated (red foreground).
  o The scenario simulation status is displayed.
  o Invalid scenarios have a checkbox which enables users to preserve 
    scenario simulation status.
    
* The generate, organize, simulate and post-process scenario dialog
  geometry (location and size) persist. The options dialog enables users to 
  reset the geometries to their defaults.
  
* The DMI Sequence Event enables users to specify the number of digits used 
  when formatting input names. This enables inputs to sort in a natural 
  order, for example Trace09 before Trace10 (rather than Trace10 before 
  Trace9).
-----------------------------
Bug Fixes
-----------------------------
RW-6425	RiverSMART assertion failure when sorting scenarios
RW-6424	RiverSMART Workspace validation errors are not displayed.
RW-6423	RiverSMART Closing log file viewer dialog crashes
RW-6336	RiverSMART When regenerating scenarios inactive scenarios aren't 
        displayed
RW-6317	RiverSMART not updating scenarios
RW-6316	RiverSMART Scenario counts are incorrect 
RW-6135	RiverSMART crashes when there are multiple model events
RW-5960	Shouldn't RiverSMART through a validation error when the RiverWare 
        event does not point to a valid executable?