DataTable- and DataRowVisualProperties are not fully backwards compatible

[cneumuel]

The quality charts of older runs cannot be viewed anymore. HL crashes with an exception:

System.InvalidOperationException: Achsenobjekt - Das automatische Intervall weist nicht den richtigen Wert auf.
   bei System.Windows.Forms.DataVisualization.Charting.Axis.EstimateAxis(Double& minimumValue, Double& maximumValue, Boolean autoMaximum, Boolean autoMinimum)
   bei System.Windows.Forms.DataVisualization.Charting.Axis.EstimateAxis()
   bei System.Windows.Forms.DataVisualization.Charting.ChartArea.SetDefaultAxesValues()
   bei System.Windows.Forms.DataVisualization.Charting.ChartArea.SetData(Boolean initializeAxes, Boolean checkIndexedAligned)
   bei System.Windows.Forms.DataVisualization.Charting.ChartPicture.Paint(Graphics graph, Boolean paintTopLevelElementOnly)
   bei System.Windows.Forms.DataVisualization.Charting.Chart.OnPaint(PaintEventArgs e)
   bei System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
   bei System.Windows.Forms.Control.WmPaint(Message& m)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The file in question (attached) is dated 04.02.2011.

[mkommend]

I've also encountered this problem when working with older GP algorithm runs. It occurs when displaying all data tables and not only with the quality chart and that's why I think it is related to the changes in the EnhancedChart or the DataTableView.

[abeham]

Thanks for reporting this issue. I looked into the problem and think I've found the cause. Actually the defect was introduced with changes made back in May. In the problematic change which is related to ticket #1465 I've added several visual properties to the DataTable, set to specific default values. I've missed adding these initializations to the storable constructor as well, as the deserializer does not use the default constructor for object initialization. All the new visual properties are set to their .Net defaults which creates an illegal configuration (axis interval set to 0-0). The storable constructor would need to also assign the default values. However another problem is that if you resaved such a DataTable these values are now stored within the file. So, I would fix this in an AfterDeserialization hook and check if the respective properties are all set to their defaults in which case I can then reset them to the default values that they should have.

I'll try to test and commit this tomorrow.

[abeham]

r6676

• Added some range checks in the DataRowVisualPropertiesControl
• Added a check to prevent axis minimum and maximum equality to avoid a crash
• Added AfterDeserialization hooks to the visual properties to detect the illegal .Net default configuration

[mkommend]

Thx for correcting this bug; everything works as expected.