Y axis labels overlapping with title after formatting

Posted by: Yifan_Zhang on 15 November 2017, 11:46 am EST

    • Post Options:
    • Link

    Posted 15 November 2017, 11:46 am EST

    Hi,

    After applying the itemFormatter for the y-axis labels, we find that the y-axis title would overlap with the labels. Please see at: http://jsfiddle.net/0q78n1ya/3/

    Can you help me fix this? Thanks.

    Btw, previously there is a relevant issue with changing the font size of the y axis labels and I believe that was well fixed:https://www.grapecity.com/en/forums/wijmo/dynamically-change-the-cha_1

  • Posted 15 November 2017, 8:35 pm EST

    Hi,

    Thank you for the sample. We were able to replicate the issue and it looks like a bug. Hence this issue has been forwarded to the concerned team for further investigation with tracking id 297650.

    As a workaround, you can set labelAngle to -45 for Y axis.

    ~Manish

  • Posted 28 November 2017, 10:01 am EST

    Any updates on this issue? Thanks.

  • Posted 28 November 2017, 7:17 pm EST

    Hi,

    This issues is under development cycle. For now you can use the workaround Manish provided above. You can track bug #297650 in the changelog file provided with Wijmo builds.

    ~nilay

    PS: We have prerelease repository @ http://prerelease.componentone.com/wijmo5/

  • Posted 25 January 2018, 10:17 am EST

    How is the progress on this issue? Thanks.

  • Posted 29 January 2018, 6:00 pm EST

    HI,

    We are sorry!

    This issue is still with the team.

    ~Manish

  • Posted 28 June 2018, 10:01 am EST

    Any updates on this issue? Thanks.

  • Posted 28 June 2018, 4:56 pm EST

    Hi,

    We are sorry indeed for the delay in this case.

    This issue is still with the team for investigation.

    ~Manish

  • Posted 26 February 2019, 11:45 am EST

    Just a follow-up to see if there are any updates with this issue? Thanks.

  • Posted 26 February 2019, 3:50 pm EST

    Hi Yifan,

    Dev team has suggested using the format property of the axis instead of itemFormatter.

    Please refer to the following code snippet and sample:

    axisY: {

    format: ‘n5’

    }

    http://jsfiddle.net/9ukdha0j/1/

    ~Sharad

  • Posted 27 February 2019, 7:43 pm EST

    Hi Sharad,

    Thanks for the reply. However, the above method may not resolve our issue as we need the itemFormatter to do some string customization. Just using the string in the format property is not sufficient (e.g., when we need to remove the trailing zeros).

    The thing is I feel like that itemFormatter is supposed to be applied before the rendering is completed, thus the chart layout could be correctly calculated. Just apply the format directly to the text elements while not changing the chart layout can be easily achieved via the html elements’ manipulation instead of the itemFormatter. I think that’s not what an itemFormatter is meant to be and it just looks like a bug to me. Please help me fix it!

  • Posted 28 February 2019, 5:42 pm EST

    Hi Yifan,

    Thanks for the additional info and your input. We have escalated the issue back to the dev team for further investigation. In the meantime, please refer to the following sample which demonstrates how we could work around the issue:

    https://stackblitz.com/edit/js-fm76vm?file=index.js

  • Posted 4 April 2019, 10:39 am EST

    Hi Sharad,

    Unfortunately, this sample does not account for footer space or legend position.

    We really hope you will be able to resolve the original issue during the current release cycle.

  • Posted 4 April 2019, 10:26 pm EST

    Hi,

    We have asked the devTeam for an update. We will update you soon with an update.

    Regards

  • Posted 12 November 2019, 12:32 pm EST

    Any updates so far? This issue becomes more and more annoying and it is really urgent now.

    We need that itemFormatter to be fixed such that it is applied before the rendering is completed and the chart layout could be correctly calculated. Just apply the format directly to the text elements while not changing the chart layout can be easily achieved via the html elements’ manipulation instead of the itemFormatter. I think that’s not what an itemFormatter is meant to be and it just looks like a bug to me. Please fix it!

  • Posted 12 November 2019, 8:57 pm EST

    Hi Yifan,

    Sorry for the delay, the issue is still with the dev team. I’ve asked the dev team to look into this case at priority and will let you know about any updates regarding the same.

    Regards

    Sharad

  • Posted 20 November 2019, 5:11 pm EST

    Hi Yifan,

    This issue has been fixed in the nightly build 5.20193.637-nightly.d20191120.t020133 and it will be included in the next hotfix release. In the meantime, we would request you to verify the fix at your end using the specified build. You may install from npm using the following command:

    npm install @grapecity/wijmo@5.20193.637-nightly.d20191120.t020133 @grapecity/wijmo.chart@5.20193.637-nightly.d20191120.t020133
    

    You may also confirm the fix using the following sample which uses the specified nightly build:

    https://stackblitz.com/edit/js-y8pz5y?file=index.js

    Regards

  • Posted 21 November 2019, 6:18 am EST

    That’s awesome. Thanks for the fix. Please let me know when the release build comes out.

  • Posted 21 November 2019, 6:59 am EST

    I would like to test out the fix on our end. But somehow I can’t manage to get the npm to work. Is there a cdn link or repo that I can test on?

  • Posted 24 November 2019, 6:05 pm EST

    Hi Yifan,

    Please refer to the following CDN links:

    https://unpkg.com/@grapecity/wijmo@5.20193.637-nightly.d20191120.t020133/index.js

    https://unpkg.com/@grapecity/wijmo.chart@5.20193.637-nightly.d20191120.t020133/index.js

    We have used unpkg to convert npm images to CDN links.

    Also, could you please let us know what issue is arising while installing the modules using npm?

    Regards,

    Ashwin

  • Posted 25 November 2019, 10:37 am EST

    Sorry it’s not about installing the modules using npm. It’s a framework issue that we use CefSharp which is quite tricky with nodejs. So I got errors using these cdn link as well. Can I have a version like from the release instead of unpacked npm images? Thanks.

  • Posted 25 November 2019, 5:58 pm EST

    Hi Yifan,

    Please refer to the link below that contains the redistributable package for the provided nightly build:

    https://www.dropbox.com/s/6248r63ppry6z05/wijmo-5.20193.637-nightly.d20191120.t020133.zip?dl=0

    ~regards

  • Posted 26 November 2019, 11:00 am EST

    Thanks for the provided build. I have tested it for our project and it works perfectly. Can’t wait to get the official release version.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels