Bug 5991: editing slot data during a run was permitted and caused problems [2]
Bug Number: 5991
Release notes (y/n): y
For Release Nums: 7.1.2, 7.2

Followup from commit [ f3c81030071d291ef56cc4ee630bca2ddf31074f ] of two days 
ago, by Patrick.

There were still a couple places where series slot edits could be effected in 
the SCT and Open Series Slot dialog -- while paused in the RPL Debugger -- 
which were resulting in either a crash or scary looking error reports.  
These were:

  (1) Incell editing in the SCT initiated by typing digits, when a cell was selected.
  (2) Entering a numeric value in the Open Slot Dialog's numeric line entry widget.

Those edits are now disabled during that time.  Also, we now BEEP in this 
latter case, AND in the analogous operation in the SCT.

I tested this with both the 5991 and 5997 bugs/scenarios. 

TECHNICAL ASIDE:  With 5997, I did get some insight into something bad 
happening in the SCT -- apparently some incomplete processing of a "state 
transition" (loosely speaking) -- related to PAUSING (breaking in) the RPL 
Debugger.  (The SctDialog's SctSlotTstepSet* _selSlotTstepSet was pointing 
to bad data, in method: SctTableDelegate::processDataCellEdit (const QString& 
editText, int row, int col)).  I had hoped to get a screenshot of that in 
the debugger, but was not able to see that again.  

... In any case, with the changes in this commit, that scenario will no 
longer be produced (i.e. because that undesirable series data editing 
operation has been disabled).  

... however, I DID discover, and fix, two uninitialized pointer fields -- 
these were not involved in these problems.  See change in QtSCT/
SctAggregationDef.cpp.