From: philw Reply-To: philw To: gnats Subject: Tabular Series Slot Report: Time Range and Description are not retained. X-Send-Pr-Version: 4.1.0 >Number: 5414 >Notify-List: >Category: RiverWare-GUI >Synopsis: Tabular Series Slot Report: Time Range and Description are not retained. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: gnats-admin >State: open >Class: sw-bug >Submitter-Id: CADSWES >Arrival-Date: Mon Nov 11 16:21:07 -0700 2013 >Last-Modified: Mon Nov 11 17:20:49 -0700 2013 >Originator: Phil Weinstein ,CADSWES,x2-5707,x2-3972 >Release: RiverWare 6.4 >Organization: unknown >Environment: System: Linux alamosa.colorado.edu 2.6.18-348.12.1.el5 #1 SMP Mon Jul 1 17:54:12 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux >Description: These two problems with the persistence of Tabular Series Slot Report (output device) configuration data are unrelated: (1) Loss of the custom series time range start and end times (for the 'Limit timesteps' option) when saving and reloading a RiverWare model. (2) Loss of the user-entered description when dismissing and reshowing the report's configuration dialog. The time range loss (#1) is due to a Tcl-based serialization problem. The custom time period 'start' and 'end' date/times are encoded as 'seconds_t' fields (64-bit integers). The Tcl load processing is using a 32-bit integer to temporarily represent the value read from the external file. This results in the loss of those date/time values. The user description loss (#2) was introduced when the configuration dialogs for several output devices were consolidated into a single new dialog class, 'SlotSetOutputConfigDlg'. (This occurred around 1-10-2012: 22 months ago). Both that dialog class AND the Tabular Series Slot Report GUI class ('GreenBookConfigPanel') provide THEIR OWN text editor widget for the output device's user description. In the case of the Tabular Series Slot Report, only the GreenBookConfigPanel's text editor widget is being initialized and shown. But the SlotSetOutputConfigDlg class is also saving its (always empty) description text to the configuration data. This is blowing away that description. >How-To-Repeat: