IssioDev

Members
 View Profile  See their activity

  • Content count

    12

  • Joined

  • Last visited

Posts posted by IssioDev

  1. Posted · Report reply

    There is an inconsistency between the plot borders on a bar2d and column2d chart which has become apparent with the 3.18.0 release.

    With a column2d chart the bottom border of each column didn't exist because there was a x-axis

    With a bar2d chart the left border of each bar is present, even if there is a y-axis

    This also doesn't occur with a stacked 2d bar chart.,

    This jsFiddle demonstrates the issue. The column chart is fine, the bar chart is not.

    https://jsfiddle.net/1d27n9ha/3/

    Screen Shot 2021-09-21 at 5.39.36 PM.png

    Screen Shot 2021-09-21 at 5.39.45 PM.png

  5. Posted · Edited by IssioDev · Report reply

    Quote

    In any of the versions, when you are setting the "yAxisMinValue" or "yAxisMaxValue" explicitly all you need to do is to first set the adjustDiv attribute to 0 to disable the automatic adjustment of divisional lines, as stated in the documentation shared in the earlier response.

    You see this is where we have a differing view. You see with 3.12.x and every version before that it works just fine. See this jsFiddle (https://jsfiddle.net/f87az9ec/4/).

    Also this isn't a bug in the automatic adjustment of the divisional lines, it's a bug in the labeling of the minimum y-axis value which is somehow linked to the setting of adjustDiv in v3.13.x

    Either way, it's a bug. "may not work properly" is the exact wording for something (ie: a bug) that used to work (3.12.x and older), doesn't work anymore (3.13.x and newer).

    Nevertheless, we have moved on, turned off adjustDiv to work around the bug and have written our own automatic divisional line algorithm as the FusionCharts version now has unwanted side-effects in v3.13 and newer.

    Personally I really don't see how this is so hard to fix, especially as it used to work.

    Anyone else who suffers the same issue when upgrading to 3.13, let me know and I'll send you the code for our algorithm so you can work around the bug. Maybe I'll post it on StackOverflow so others can work around the bug.

  6. Posted · Report reply

    I think you are saving that you broke it in 3.13 and here is the workaround. You know this works in all versions prior to 3.13 don't you?

    All in all I can work with this, it is disappointing though that the "automatic internal divisional line algorithm" has broken but I can turn it off and replicate the work that your algorithm is doing myself.

    Displaying the 0 on the y-baseline shouldn't really be a function of the "automatic internal divisional line algorithm" which really is the point isn't it.