Released: Oct 10, 2024

v12.1.1 での更新項目

機能

• HexagonShape available for Points and Markers - The hexagon shape is now available for the Points (series.PointStyle.Shape) and Markers (Symbol.Shape) properties. Like other geometrical shapes, the Hexagon shape allows body coloring with a two-color gradient, as well as with a separate color for the border. The hexagon shape also supports export to raster/bitmap or vector images.
• Improved 3D Interactions - In this release, 3D interactions like zooming, rotation and panning have been improved for objects that render as large surfaces, e.g., SurfaceGridSeries3D, SurfaceMeshSeries3D, and MeshModel. The performance on a mid-level computer will increase two-fold, and when using a high-end graphics card, the speed can be up to 10x faster. Similarly, 2D interactions like zooming and panning will be much faster for the FreeformPointLineSeries when the point count is in millions.
• Other Improvements
  • Large ValueRangePalette Improvement - ValueRangePalette is a property that can be used by line series, intensity series, polar line series, surface 3D, etc. Previously, if the palette had to load more than 20 steps, the chart became slow. Now, the user can feature hundreds of steps in the palette without any performance penalties. However, to create a smooth palette (color bar), you don't need to use hundreds of steps instead, you can use the PaletteType.Gradient with only a few colors that will interpolate in between.

不具合の修正

• Improved VolumeModel binding - While the LightningChart MVVM edition works with VolumeModel, the binding to this class did not work properly. VolumeModel binding errors have now been fixed and overall performance has been improved.
• Improved zooming behavior for XY block-line-series - While XY block-series (SampleDataBlockSeries, LiteLineSeries, DigitalLineSeries) greatly improved application performance and reduced memory usage, in certain circumstances they caused AccessViolationException in the past. In particular, when the chart has a lot of points (e.g. 200M for LiteLineSeries) and deep zoom-in is performed. Now the issue has fixed and zooming will not cause AccessViolationException.