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 am using a stacked bar chart to show two data series. The values of one of them are multiplied with -1 to go into the negative direction of the y-axis. The purpose is to compare two series.
However:
I noticed that the Y-Axis scaling is not working as expected when using a stacked bar chart. When setting stacked: false the Y-Axis works as expected, but this gives not the visualization that I want to get out of the chart.
Only for stacked charts new MinMax values are calculated (because of the stacking). But in calculating those values, the whole range of the chart is used. This way the global maximum is used to calculate the maximum of the y-axis.
For the minimum, the value in the relevant window is saved into lowestYInAllSeries in line 256 und reapplied in the next block in line 279 since it's a bar chart.
It seems the function/function call has te be changed in a way to only work with the selected x-axis indices.
Description
I am using a stacked bar chart to show two data series. The values of one of them are multiplied with -1 to go into the negative direction of the y-axis. The purpose is to compare two series.
However:
I noticed that the Y-Axis scaling is not working as expected when using a stacked bar chart. When setting
stacked: false
the Y-Axis works as expected, but this gives not the visualization that I want to get out of the chart.Steps to Reproduce
Expected Behavior
I would like to have the Y-Axis to scale in the positive and negative range correctly on a stacked bar chart.
Actual Behavior
The Y-Axis is not scaling correctly in both directions,
Screenshots
Non-stacked:
Stacked:
I would expect to see the same Y-Axis that is shown in the non-stacked Version when using a stacked bar chart.
Reproduction Link
https://codepen.io/Loahrs/pen/BaXbgma
The text was updated successfully, but these errors were encountered: