#2798 Be more aggressive about keeping invalid datumRanges out of the dom

[Jeremy Faden]

Here's a script which results in a DatumRange containing fill, and this gets into the DasAxis, causing runtime errors at draw time. This makes the GUI unusable. The code needs to be more aggressive in not allowing such values to get into the DOM. This may cause problems where there are brief transitions which have invalid states, so a thorough study of the change will be needed.

[Jeremy Faden]

Here's the script:

setScriptTitle('Demo Runtime Error in Render')
setScriptDescription('''It's fairly easy to get a fill value into the data and cause it to throw a runtime error each time 
a paint or render occurs.  I need to identify the path that allows fill data to get in there, and
ran across this demo which shows.''')

l= getDataSet('vap+cdaweb:ds=OMNI2_H0_MRG1HR&id=DST1800&timerange=2004')
x= xtags(l)
x.putProperty(QDataSet.UNITS,Units.t2000)
plot( x, l )

There are probably simpler scripts which demo the problem.

[Jeremy Faden]

I've made it so that dom.setTimeRange and Axis.setRange both ignore DatumRanges with invalid data, and I'll be watching to see what problems that causes.

[Jeremy Faden]

Sadie and I ran across this bug when working on a process.