LightningChart® .

NET Changelog

LC .NET version 10.5.1.1

Released June 15th, 2023.

This is the sixth major release of the v10 LightningChart® .NET line. In this release we added
new features and fixed several bugs. We added DataCursor class (advanced data tracking tool)
for 3D, Polar and Smith views/charts. In addition, we introduced TransparencyRenderMode
property to 3D-surface-series and PointLineSeries3D for better handling of transparent colors.

DataCursor new feature for automated data tracking

Now all 3D, Polar and Smith series could be explored with DataCursor: class/object shows
series data value at or near mouse position. Previously LightningChart provided various tools to
implement data tracking functionality but that required some extra coding by the user. Features
and functionality of DataCursor is similar to XY DataCursor, which was released in version
10.4.1. DataCursor consists of axis labels, result table, color bar and haircross lines. Each
individual item of DataCursor could be configured. Visible property of DataCursor is disabled
by default (to avoid backwards compatibility breaks). Each series has CursorTrackEnabled
property to control DataCursor automated tracking on it.

3D TransparencyRenderMode property/feature

3D-surface-series (SurfaceGridSeries3D, SurfaceMeshSeries3D and WaterfallSeries3D) and

PointLineSeries3D now have TransparencyRenderMode property. LightningChart offers 3
options for handling transparency of the surface: Unordered, ShaderApproximation and
OrderingTriangles. The new feature helps to mitigate artifacts and improve translucent object
handling in the chart. This new way to handle translucent surface/lines is available only when
DirectX 11 renderer is used (i.e., RendererDeviceType is either HardwareOnlyD11 or
SoftwareOnlyD11).

Note: In this release the target framework version for LightningChart's library updated to .NET
Framework 4.6.2. Any user’s project, which uses LightningChart's library, should set target
framework at least .NET Framework 4.6.2. Any newer version (like .NET Framework 4.8 or
.NET 7.0) is fine as well.

Check out the rest of the changelog for detailed information.

This is a full listing of the changes in version 10.5.1 against 10.4.1

New features
• 3D surface-series and line-series has TransparencyRenderMode property/feature now
3D-surface-series (SurfaceGridSeries3D, SurfaceMeshSeries3D and WaterfallSeries3D) and
PointLineSeries3D has TransparencyRenderMode property. LightningChart offers 3 options
for handling transparency of the surface: Unordered, ShaderApproximation and
OrderingTriangles. The new feature helps to mitigate artifacts and improve translucent object
handling in the chart. This new way to handle translucent surface/lines is available only when
DirectX 11 renderer is used (i.e., RendererDeviceType is either HardwareOnlyD11 or
SoftwareOnlyD11).

• Polar DataCursor new feature for automated data tracking in the chart
Now all Polar series could be explored with DataCursor: class/object shows series data value
at or near mouse position. DataCursor consists of Amplitude & Angle axis labels, result table,
color bar and haircross lines. Each individual item of DataCursor could be configured.
Visible property of DataCursor is disabled by default (to avoid backwards compatibility
breaks). Each Polar series has CursorTrackEnabled property to control DataCursor automated
tracking on it. In many respects Polar DataCursor is similar to XY, or other Views.

• 3D DataCursor new feature for automated data tracking in the chart

Now all 3D series could be explored with DataCursor: class/object shows series data value at
or near mouse position. DataCursor consists of 3 axes labels, result table, color bar and
haircross lines. Each individual item of DataCursor could be configured. Visible property of
DataCursor is disabled by default (to avoid backwards compatibility breaks). Each 3D series
has CursorTrackEnabled property to control DataCursor automated tracking on it. In many
respects 3D DataCursor is similar to XY, or other Views.

• Smith chart DataCursor is new feature for automated data tracking in the chart
Now Smith chart series could be explored with DataCursor: class/object shows series data
value at or near mouse position. DataCursor consists of Real and Imaginary axis labels, result
table, color bar and haircross lines. Each individual item of DataCursor could be configured.
Visible property of DataCursor is disabled by default (to avoid backwards compatibility
breaks). Smith chart series has CursorTrackEnabled property to control DataCursor
automated tracking on it. In many respects Smith chart DataCursor is similar to XY, or other
Views.
Improvements
• Better handling possible SharpDX.Direct3D9.Device.Reset exception
If for some reason Rendering Engine need to be disposed and recreated,
IDirect3DDevice9::Reset needs to be called. In some rare event system message handling
may coincide with this call (which will lead to exception). To avoid exception, now try-catch
loop was added to handle possible exception and allow chart to continue as normal. Warning
ChartMessage will be raised to inform user that RenderingEngine disposal and reset may be
incomplete.

• The target framework version for LightningChart's library update to .NET Framework 4.6.2
- [BCB]
Previously the target framework version for LightningChart's library was .NET Framework
4.5.2. .NET Framework 4.5.2, 4.6, 4.6.1 reached End of Support on April 26, 2022. After this
date, Microsoft will no longer provide updates including security fixes or technical support
for these versions. .NET Framework 4.6.2 and newer versions to support newer digital
certificates (for the installers). .NET Framework 4.6.2 will continue to receive security fixes
or technical support by Microsoft.
Error fixes
• HollowYAxis-marker interaction now obeys segment boundaries
Previously in segmented/stacked YAxes layout, HollowYAxis-marker was 'seen' beyond its
segment. For example, it was possible to drag marker from completely different segment.
Now the issue is fixed, and marker could be dragged only inside its segment.

• Fixed LineSeriesCursor's TrackPoint issue, if DataBreaking Enabled

Previously LineSeriesCursor's TrackPoint may be rendered incorrectly, if adjacent series had
DataBreaking value. This is now fixed.

• Fix possible NullReferenceException with logarithmic YAxis

This error only appears in version 10.4.1.1. When logarithmic YAxis is used and IF minor
Ticks and Grid is hidden OR IF CustomTicks enabled, chart will get Null-Reference-
exception. Now it is fixed.

• Fixed serialization error with DataCursor

Previously, then chart component is dropped from WinForms toolbox, text (TextColor)
remains invisible in ViewXY DataCursor Results table. Now the issue is fixed.

• Fixed UWP application touch screen operation for XY and 3D views

Previously in UWP applications, XY or 3D chart behaved erratically when touch-screen
pinch-zooming or panning was performed. This is now it is fixed.

• Fixed chart rendering for DeviceType = HardwareOnlyD9, with trial license

Previously (version 10.x) chart/application was crashing, if only trial license installed and
DeviceType set as HardwareOnlyD9/AutoPreferD9. Now the error is fixed.

• Prevented too large ClipAreas from crashing application on GDI export

It is possible to set ClipAreas for XY series, which prevent part of the series data from
rendering. However, previously setting very large ClipAreas (far outside visible range) may
lead to exception on GDI export (vector format image). This is now fixed.

• Prevented extremely large ClipAreas from causing rendering problem

Previously, the very large ClipArea's boundaries value (Begin and End property), may lead to
rendering issue. For example, series may not even rendered, when SoftwareOnlyD11 is used.
Now the issue is fixed.

• Chart title now visible when chart exported as EMF format

After some changes in v10.4.1.1 Chart title was not visible when exported to EMF file
format. The issue is fixed and the title is visible in all vector image exports.

• Prevented some needless crashes if SegmentIndex is accidentally set

Previously, if YAxis.SegmentIndex was set to higher number than
ViewXY.AxisLayout.Segments, the Chart was crashing even if Segmented layout was not
used.

• Fixed possible IndexOutOfRangeException with BlockSeriesBase

Previously it was possible to get IndexOutOfRangeException in some cases when data is
added, cleared and added again to BlockSeriesBase (DigitalLineSeries,
LiteFreeformLineSeries, LiteLineSeries and SampleDataBlockSeries). The series are now
properly reset. In addition, a small improvement has been done by reducing unnecessary
rendering data creation.
• Fixed possible LegendBox incorrect size calculations
Previously, with some settings LegendBox's size was incorrectly calculated. In particular,
when Unit text font was very big and while Series.Title.Text was a empty string. Now the
issue is fixed.

• ConstantLine aligned with YAxis tick/grid, if they have same value

Previously ConstantLine may be not align with YAxis tick or grid by 1 pixel. This is now
fixed.

• Smith chart Imaginary grid's label now always cleared

Previously, if ViewSmith.Axis.GridType was set as DivCount and Axis.GridImg.Visible was
disabled, then Imaginary grid's label was still shown. This is now fixed.

• BlockSeries's OffsetY value is taken into account then XY DataCursor reads values
Previously XY DataCursor tracked line-series value incorrectly if OffsetY was not set to 0.
This is property of BlockSeries type (SampleDataBlockSeries, DigitalLineSeries,
LiteLineSeries, LiteFreeformLineSeries). Now the error is fixed.

• Prevented possible IndexOutOfRangeException with block-series in Sweeping

Previously when SampleDataBlockSeries is used in data-streaming application, possible
IndexOutOfRangeException may be encountered. In particular, when XAxisScrollMode is
Sweeping, and chart zoomed/resized at wrong time. This issue now fixed and rendering data
rebuild correctly when zoomed.

Backwards compatibility breaks

API changes
• The target framework version for LightningChart's library update to .NET Framework 4.6.2
Any user's project, which uses LightningChart's library should set target framework at least
.NET Framework 4.6.2. Any newer version (like .NET Framework 4.8 or .NET 7.0) is fine as
well.