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 seen this bug in radar chart, but not sure if applicable to other charts.
Due to the nature of adaptive calculating for the intervals,
varrawInterval= range / Double(labelCount);
will have different range, so sometimes, the actual n value in
for (f = first; f <= last; f += interval){++n;
}
will have different values. if we change the data, n can be 4 or 5. so the _yAxis.entries can be messed up.
For example,first time:
(lldb) po _yAxis.entries
[0.0, 400.0, 800.0, 1200.0]
when I change the data:
(lldb) po _yAxis.entries
[0.0, 100.0, 200.0, 300.0, 400.0, 500.0]
Seems good hah? But if I change the data back to the first one:
(lldb) po _yAxis.entries
[0.0, 400.0, 800.0, 1200.0, 400.0, 500.0]
The trick is the second data will have 6 elements, while the first only has 3. This will cause the _yAxis.axisRange to a wrong value, and chart.factor, and the rendering then.
However, I don't know how to separate different commit to different pull request. GitHub just merged all my commits into one.
The text was updated successfully, but these errors were encountered:
liuxuan30
changed the title
bug:_yAxis.entries will not be cleaned up in computeAxisValues in radar chart
[BUG] _yAxis.entries will not be cleaned up in computeAxisValues in radar chart
Jun 18, 2015
I have seen this bug in radar chart, but not sure if applicable to other charts.
Due to the nature of adaptive calculating for the intervals,
will have different range, so sometimes, the actual n value in
will have different values. if we change the data, n can be 4 or 5. so the _yAxis.entries can be messed up.
For example,first time:
when I change the data:
Seems good hah? But if I change the data back to the first one:
The trick is the second data will have 6 elements, while the first only has 3. This will cause the _yAxis.axisRange to a wrong value, and chart.factor, and the rendering then.
I have fixed this in liuxuan30@48d0804
However, I don't know how to separate different commit to different pull request. GitHub just merged all my commits into one.
The text was updated successfully, but these errors were encountered: