Chart: SplineSeries rendering is not correct in certain scenarios
Resizing the window containing a CartesianChart with SplineSeries leads to some incorrect rendering between points:
6 comments
ADMIN
Yana
Posted on:15 Jul 2022 11:59
Hello Sebastien,
Thank you for sending the additional details - we'll take this use case into account as well.
I agree the spline series rendering is currently not usable, I am sorry for the caused inconvenience.
Regards,
Yana
Progress Telerik
Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.
Sébastien
Posted on:13 Jul 2022 12:36
I simplified the sample to have only 4 and 5 points. The splines does not work. The rendering is actually worse with few points.
I am afraid I cannot commit to a certain timeframe for this issue - I understand this makes the spline series not usable to some extent, still, for the time being it is not with high priority on our side - priority is calculated according to many factors, such as demand, severity, complexity, and other.
As a temporary workaround, you can try not to show too many points at a time, in order to avoid rendering the loop - just display small portions of the spline series.
I forgot to add in the last comment is there is no alternative, your LinesSeries have abysmal performance https://feedback.telerik.com/uwp/1571209-chart-inconsistency-in-rendering-performance-between-line-and-splineseries?_ga=2.100365017.673168840.1657545927-613589072.1649385393
Sébastien
Posted on:11 Jul 2022 13:28
As I see in this bug report, it is in "unplanned" state. That's fine it is 11 days ish new. Do you have a rough estimate when the bug will be in planned states? That bug makes the whole usage of Splines not usable. Since the bug is also in WinUI and UWP, it is probably in your other SDKs especially if the rendering engine uses shared code.
Thank you
Sébastien
Posted on:30 Jun 2022 14:44
For the record, the same bug happens in WinUI apps (not only UWP).