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'd offer a fix for this but this is my very first look at ios-charts and I've only got about 20 minutes in on this project. With that said, the bug is exposed in the ChartsDemo using the Sinus Bar Chart but reducing the element count to 1 by dragging the control at the bottom of the chart as far to the left as possible.
BarChartRenderer.drawDataSet attempts to pixelize the rect to be drawn on line 124 by calling trans.rectValueToPixel(&barRect). When there is only one element to be drawn, barRect is (-0.3, 0.0, 0.6, 0.0) before the call and (nan, nan, nan, nan) after the call. Apparently, the affine transform performed in rectValueToPixel does not like something about the incoming rect.
None of the other charts allow less than two elements to be presented so, without some additional futzing, I was unable to see if this bug is manifest for single-element bar charts.
(If I get time, I'll research further.)
The text was updated successfully, but these errors were encountered:
I'd offer a fix for this but this is my very first look at ios-charts and I've only got about 20 minutes in on this project. With that said, the bug is exposed in the ChartsDemo using the Sinus Bar Chart but reducing the element count to 1 by dragging the control at the bottom of the chart as far to the left as possible.
BarChartRenderer.drawDataSet attempts to pixelize the rect to be drawn on line 124 by calling trans.rectValueToPixel(&barRect). When there is only one element to be drawn, barRect is (-0.3, 0.0, 0.6, 0.0) before the call and (nan, nan, nan, nan) after the call. Apparently, the affine transform performed in rectValueToPixel does not like something about the incoming rect.
None of the other charts allow less than two elements to be presented so, without some additional futzing, I was unable to see if this bug is manifest for single-element bar charts.
(If I get time, I'll research further.)
The text was updated successfully, but these errors were encountered: