Axis object doesn't reject illegal ranges, instead uses runtime error to reject. I saw a runtime error and was able to demo the problem by setting an axis range to "0 to 0". This should raise a nicer error message or reject the input in the GUI.
See https://github.com/das-developers/das2java/issues/121 where I started thinking this should be handled in Das2.
The Axis object now ignores zero-width DatumRanges just like it does nulls.
The DatumRangeEditor object allows 0 to 0 as a valid DatumRange (which is true though not in this case).
I've added a control to the DatumRangeEditor which will reject zero-width inputs, and the axis tab uses this option.
I'm closing this ticket as fixed.
See https://github.com/das-developers/das2java/issues/121 where I started thinking this should be handled in Das2.
The Axis object now ignores zero-width DatumRanges just like it does nulls.
The DatumRangeEditor object allows 0 to 0 as a valid DatumRange (which is true though not in this case).
I've added a control to the DatumRangeEditor which will reject zero-width inputs, and the axis tab uses this option.
I'm closing this ticket as fixed.