RiverWare 6.1: Qt4 Port of MRM (Multiple Run Management) Dialogs
Phil Weinstein, CADSWES -- See also Port UI change documentation

Responses to David's initial review comments, in his 1-28-2011 e-mail ... "Here are some more comments that I found when trying to set up a model to be used for documentation purposes. I updated the doc, but am going to wait until we decide on these things before updating screenshots". -David

Status [2-01-2011]: I've completed the items I was sure we would want to proceed with. The remaining items need more discussion. -Phil

  David' Review Comments (1-28-2011)
    Phil's Resolution Status (2-01-2011)
1 (previously sent) ... Choose Index Sequential with 2 or more runs and 2 input DMIs, Click on Pairs and click on Distributed Runs. Then click on Combinations and the Distributed Runs toggle is disabled but the tab is still there.
    DONE See 1-31-2011 notes (first set of changes MrmRunEditDlg.cpp)
2 When you first open a config, it opens to the Output tab. It should open to the Description tab.
    DONE The first time in the RiverWare session, the initial tab in any MRM Config Editor dialog is the Description tab (which is the leftmost tab). The next time any MRM Config Editor dialog is opened, the most recently accessed tab (which is visible in the particular instance of the dialog) is initially shown. The mechanism applies also to when the current tab is removed -- the most recently accessed tab among the remaining tabs is shown. See 1-31-2011 notes (second set of changes).
3 Concurrent Runs tab and Consecutive Runs tab. Can't resize columns.
    defer This was deliberate. All columns are set to expand to the full width of the column content. It seemed that with the new list which highlights the full selected row, for this application, the user would appreciate not having to mess with individual column widths. I thought that just having the user make the whole dialog wide enough (or turning off "Details") to see the data was a better choice. This, I think, is even more reasonable with the change of the Policy column to show only Ruleset filenames (and not their whole path) -- see next item.
4 Concurrent Runs tab with Details shown and rulesets. It would be good to show just the ruleset name not the full path. Then show the full path in a tooltip. We did most of that in the old version.
    DONE See 2-01-2011 notes (the change to MrmRunTreeView.cpp).
5 Consecutive Runs tab ...
5a Perhaps we can just remove Consecutive mode and not have to deal with some of these issues?
    defer (Note: much of the complexity of the Run list is to support Consecutive mode).
5b Is policy relevant to consecutive runs? Having policy is OK, but it should allow at most 1 policy.
    defer I'm not sure that that conclusion is correct. When you have multiple policies (rulesets), the consecutive runs DO rotate through those policies (as you add runs in the run tab) -- that could be useful. When this isn't desired, the user would include only one ruleset.
5c Are Input DMIs relevant to consecutive?
    defer ... Similarly, they seem to be, at least looking at the behavior of the Run list.
6 Is there any chance we could re-arrange the "Input" information? There should be an upper level toggle that specifies that you will have inputs, but then the Input DMI, Traces, Index Seq. toggles should be on the input tab itself. As it is now, it is really hard to document and explain.
    defer It seems to me that those settings are useful to see also when the "Run" tab is shown. Changes to those controls have an immediate effect on the Run list, and that's helpful to understand what's going on.
7 INPUT DMIs area: "Append Dmi" should be "Append DMI"
    DONE  
8 The Combinations radio button should be selected (and shown that way) even when that area is grayed out. The default behavior is Combinations. Only in certain situations is the Pairs option available. Right Bill?
    DONE See the 2-01-2011 notes (first set of MultiRunEditDlg.cpp changes).
9 According to Bill, the Traces option shouldn't be possible if Input DMIs is not selected.
    DONE See the 2-01-2011 notes (second set of MultiRunEditDlg.cpp changes) ... "Traces" is made unavailable when the "Input DMIs" checkbox is off -- AND the Input mode is reverted from "Traces" to "None" when that checkbox is turned off.
10 If you specify a non-one First Trace or an non-zero Initial Offset, shouldn't the Concurrent Runs tab display that information? I.e. it should only show the runs that will actually be made, not the full set. Or possibly show the full set but only highlight the runs that will be made.
    defer I'm not understanding David's observation. Changing the Initial Offset OR the Interval doesn't effect the sequence of runs -- that only effects the "rotating" of series data inputs within each of those runs. The information in the "Index Seq." column (when that column is shown, with "Details" on), does describe each run's series data "rotation".

--- (end) ---