-
-
Notifications
You must be signed in to change notification settings - Fork 6k
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
CombinedChartView half first/last bar in single bar case, and fitBars defect #3186
Comments
x-axis labels are not calculated correct as well as the issues with the bars being cut in half. And then there is the old bug with labels in stacked bars not fitting - I had a fix for this in the old version so I need to figure out how to backport the fix. Not related to to this issue but these two are blocking my release so I will dig through the code a bit and see if I can get them resolved. Got the labels in the stacked bars better but still some scenarios where labels may overlap |
please open another issue to track your label issues. For the first one, I already documented the reason and workaround so far. |
Cool, I guess I do not understand the workaround proposed, will re-read your comments and see if I can come to grips with it. The other issue is #620 so my fix for the labels should go there as before. |
For the x-axis labels issue, my current workaround is to rotate the labels -15 degrees. |
Currently, combined chart with single bar will cut half of first and last bar.
In bar chart,
fitBars
is not working as expected, it's default disabled, but somehow the bars are just showing correctly, while turning on, it have more space. buggyProblem 1: fitBars conflict with xAxis.spaceMin/Max
see #3186 (comment)
Problem 2: combined chart bars being cut off
see #3186 (comment)
Solution
For Problem 1, we can fix the conflict and update tests
For Problem 2, so far I don't have a descent solution to unify them, as all sub chart data shares the same xAxis, and to align different charts together, tweaking the x values and axisMinimum/Maximum instead of xAxis's internal min/max values or use multiple matrix and shadow xAxis is a much lower cost.
The text was updated successfully, but these errors were encountered: