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
When attempting to render a dataset with 50,000 data points in a chart using the Sfcartesian Flutter library, the rendering stops or performs extremely poorly. The goal is to display all 50,000 data points within a single chart while maintaining smooth performance and responsiveness.
Steps to Reproduce:
Use the Sfcartesian widget to create a simple line chart or scatter chart.
Populate the chart with a dataset of 50,000 data points.
Attempt to view the chart.
Expected Behavior:
The chart should render all 50,000 data points and remain interactive (e.g., zoom, pan, etc.).
Observed Behavior:
The rendering stops or becomes extremely slow.
The chart fails to maintain responsiveness and interactivity.
Could you provide guidance or enhancements to the library to support rendering larger datasets efficiently? If this limitation is intentional, are there any recommended best practices or workarounds to address this? Thanks in advance!
The text was updated successfully, but these errors were encountered:
When attempting to render a dataset with 50,000 data points in a chart using the Sfcartesian Flutter library, the rendering stops or performs extremely poorly. The goal is to display all 50,000 data points within a single chart while maintaining smooth performance and responsiveness.
Steps to Reproduce:
Use the Sfcartesian widget to create a simple line chart or scatter chart.
Populate the chart with a dataset of 50,000 data points.
Attempt to view the chart.
Expected Behavior:
The chart should render all 50,000 data points and remain interactive (e.g., zoom, pan, etc.).
Observed Behavior:
The rendering stops or becomes extremely slow.
The chart fails to maintain responsiveness and interactivity.
Could you provide guidance or enhancements to the library to support rendering larger datasets efficiently? If this limitation is intentional, are there any recommended best practices or workarounds to address this? Thanks in advance!
The text was updated successfully, but these errors were encountered: