You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some data need to use the linear graph display series, series number is variable , so I need to use the dynamic sequence, I hope to meet with empty data corresponding to the position line is disconnected, when I alone to create multiple sequence diagram shows the correct, however, when I use dynamic sequence chart shows data errors, charts ignore null values show a continuous line, another one of my projects,the line graph is disconnected from the null value, but some of the neighboring data is not properly connected, I want to know why and how to solve.
The text was updated successfully, but these errors were encountered:
@fengjunling Null values are not supported in the Chat control. Basically, internally the null values are presented as NaN values and because of that they are visualized in the way you observed. I suggest you prevent rendering null points in your Chart.
I believe supporting null values will be a nice addition in our Chart control, so I will mark the issue as a feature request. Building it however won't be an easy task, because of that currently I cannot provide you with more details from where you can start building that feature.
I hope the provided information will be helpful for you.
I have some data need to use the linear graph display series, series number is variable , so I need to use the dynamic sequence, I hope to meet with empty data corresponding to the position line is disconnected, when I alone to create multiple sequence diagram shows the correct, however, when I use dynamic sequence chart shows data errors, charts ignore null values show a continuous line, another one of my projects,the line graph is disconnected from the null value, but some of the neighboring data is not properly connected, I want to know why and how to solve.
The text was updated successfully, but these errors were encountered: