Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scatter Series geometry size calculation - option to consider all series #1555

Open
DavidWiseman opened this issue Aug 1, 2024 · 1 comment
Labels
new feature priority 1 might not be fixed in the next release of the library, but it will soon!

Comments

@DavidWiseman
Copy link

Is your feature request related to a problem? Please describe.
I have multiple series in a scatter chart. The size of the bubbles appears to be based on the weight within the series only. My situation is that I want to compare SQL execution plans. Each plan is a series with a different color. I want to plot the durations on the Y axis and time on the X axis. The weight of the bubble should be based on the count of executions. At the moment one plan might have a max of 10 executions and the other 1000 - each currently producing the same size bubble. The plan/series with a max of 10 should take into account that the max across all the series is 1000 and produce a smaller bubble.

Describe the solution you'd like
Ideally there would be an option to take into consideration the max/min value across all series.

Describe alternatives you've considered
I can add fake data points to each series with the min/max value across all series. The X asis date time is set to DateTime.MinValue which is below the min limit for the chart. These fake points don't get plotted but the values ensure that the weighting is consistent across the series.
This workaround is good for me, but it would be nice to have a built in option. If you decide not to implement the feature, the workaround above might help someone else.

Great work on this charting library. 🙏👍

@beto-rodriguez
Copy link
Owner

Hi and thanks for the report!

This makes sense! I'll schedule this for a future release!

@beto-rodriguez beto-rodriguez added new feature priority 1 might not be fixed in the next release of the library, but it will soon! labels Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature priority 1 might not be fixed in the next release of the library, but it will soon!
Projects
None yet
Development

No branches or pull requests

2 participants