Wijmo5 FlexChart Title Line Break/Wrap

Wijmo5 FlexChart Title Line Break/Wrap

Posted by: marcus.nixon on 18 April 2018, 2:20 am EST

• 

  marcus.nixon

  • Post Options:
  • Link
    Copy

  Posted 18 April 2018, 2:20 am EST

  I am converting a chart from Wijmo 3, where we could insert \r\n to create a new line in an axis title (chartOptions.axisY.title), but that is being ignored in flexchart.

  When I looked at the SVG generated in v3, it used to insert tspan elements into the text element for each section split by \r\n, but this functionality seems to have been lost as all it does now is just put it all into one text element. Worse still, that does not seem to wrap either, which means it looks poor if the text is larger than the chart.

  Any idea how to get around this limitation please? Cheers.

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 18 April 2018, 8:29 pm EST

  Hi,
  
  You may add text in multi-line using tspan for header text. Please refer to the attached sample.

  ~Manish

  FlexChart_MultiLine_header.zip

• 

  marcus.nixon

  • Post Options:
  • Link
    Copy

  Posted 19 April 2018, 7:53 pm EST

  When you export the chart to a jpeg, it also prints out the html used to wrap the labels i.e. it prints the tspans!

  Is there a way around this?

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 20 April 2018, 12:14 am EST

  Hi Marcus,
  
  We are sorry, we are unable to replicate the issue at our end with latest build 5.20181.436. Please find the attached sample and exported image.

  ~Manish

  FlexChart_MultiLine_header_updated.zip[img]https://gccontent.blob.core.windows.net/forum-uploads/file-621f7007-ffc9-4cad-88b4-3a1418fd8d1a.jpeg[/img]

• 

  marcus.nixon

  • Post Options:
  • Link
    Copy

  Posted 20 April 2018, 12:38 am EST

  Add the following line to your demo above and run it under IE.

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 23 April 2018, 10:11 pm EST

  Hi,
  
  We are sorry for the delay in response.

  We are able to replicate the issue at our end and it seems a bug. Hence, this issue has been forwarded to the concerned team for further investigation with tracking id : 319007.

  We will let you know as we get any update on this.

  ~Manish