Skip to content

Releases: kirsan31/winforms-datavisualization

1.10 preview 2

17 Oct 07:19
Compare
Choose a tag to compare
1.10 preview 2 Pre-release
Pre-release
  • More performance improvements.
  • .NET9 support.
  • ReadOnlySpan<char> overloads for name find methods in ChartNamedElementCollection and DataPointCustomProperties. .NET9 only.

NuGet.

1.10 preview

09 Oct 09:33
Compare
Choose a tag to compare
1.10 preview Pre-release
Pre-release
  • Per-Monitor DPI awareness (PerMonitorV2) support.
  • Lots of performance improvements.
  • Old small bugs fixes.

Breaking changes.

  • Deprecated #SER keyword removed - use #SERIESNAME instead.
  • DataPointCustomProperties.Item[int] indexer removed. It was no use anyway.
  • IDisposable Interface implementation removed from: AnnotationCollection, SeriesCollection, LabelStyle, StripLinesCollection, StripLine, Title, TitleCollection, LegendCellColumn, LegendCell, LegendCellCollection, LegendItem, LegendCellColumnCollection, Legend, LegendCollection, Annotation and all it's derived classes except PolylineAnnotation.

NuGet.

1.9.2

11 Feb 15:13
Compare
Choose a tag to compare

1.9.2

  • .NET 8 support.
  • Small bug fixes.

NuGet.

1.9.1

29 Oct 18:20
Compare
Choose a tag to compare

1.9 regressions fix.

  • Fixed drawing of the beginning of line graphs. #46
  • Fixed drawing of visible Empty points in line graphs.
  • Reverted HitTest bug fix (#42).

NuGet.

1.9

15 Oct 15:13
Compare
Choose a tag to compare
1.9

Changes from 1.8

  • Many additions and fixes in HitTest for lines and points charts both in 2D and mainly in 3D modes.
    #39, #40, #41, #42.
  • Optimizations and bugs fixes (including #35).

Breaking change.

The algorithm for determining indexed series has been changed. Previously, a series was considered indexed if the IsXValueIndexed flag was set or if all its data points had an X-axis value equal to 0.
To draw a vertical line at an X-axis value of 0, you had to set a custom flag, IsXAxisQuantitative.
Now, a series is considered indexed only if the IsXValueIndexed flag is set. The custom flag, IsXAxisQuantitative, has been removed. This change also improves performance, especially for series with many X-axis zero points.

Recommended actions:

  • If your indexed series were defined solely by having all their X-axis values equal to zero, you need to set the IsXValueIndexed flag for these series.
  • If you were using the IsXAxisQuantitative flag, you should remove it.

Changes from 1.9 preview

  • Revert (from b37e8e9) DataPointCollection.Clear() optimization for already empty collections. Fix #44.
  • Drastically improve xml serialization speed.
  • Fix #43. Some corrections.

NuGet.

1.9 preview

09 Sep 10:15
Compare
Choose a tag to compare
1.9 preview Pre-release
Pre-release
  • Many additions and fixes in HitTest for lines and points charts both in 2D and mainly in 3D modes.
    #39, #40, #41, #42.
  • Optimizations and bugs fixes (including #35).

Breaking change.

The algorithm for determining indexed series has been changed. Previously, a series was considered indexed if the IsXValueIndexed flag was set or if all its data points had an X-axis value equal to 0.
To draw a vertical line at an X-axis value of 0, you had to set a custom flag, IsXAxisQuantitative.
Now, a series is considered indexed only if the IsXValueIndexed flag is set. The custom flag, IsXAxisQuantitative, has been removed. This change also improves performance, especially for series with many X-axis zero points.

Recommended actions:

  • If your indexed series were defined solely by having all their X-axis values equal to zero, you need to set the IsXValueIndexed flag for these series.
  • If you were using the IsXAxisQuantitative flag, you should remove it.

NuGet.

1.8

18 Mar 15:07
Compare
Choose a tag to compare
1.8

Changes from 1.7

Small breaking change.

If you use Axes auto min \ max values and call DataPointCollection.Clear() method for already empty collection:

  • Old behavior - axes min \ max values will be recalculated on next chart paint.
  • New behavior - axes min \ max values will not be recalculated.

Changes from 1.8 preview

  • Small bug fixed - in some cases for axes value of 0, labels could be shown as -0.

NuGet.

1.8 preview

14 Feb 13:04
Compare
Choose a tag to compare
1.8 preview Pre-release
Pre-release

Small breaking change.

If you use Axes auto min \ max values and call DataPointCollection.Clear() method for already empty collection:

  • Old behavior - axes min \ max values will be recalculated on next chart paint.
  • New behavior - axes min \ max values will not be recalculated.

NuGet.

1.7

10 Jan 20:30
Compare
Choose a tag to compare
1.7
  • 1.7 release.
  • Tiny performance optimization since 1.7 preview.

NuGet.

1.7 preview

30 Dec 18:47
Compare
Choose a tag to compare
1.7 preview Pre-release
Pre-release
  • All collection editors are ported - control now have full design time parity with .net framework version.
  • Small bug fixes and improvements.

NuGet.

This is a pre-release due to test that designer working well. Runtime part must be stable.