React FlexChart itemFormatter - change Symbol size of specific point

React FlexChart itemFormatter - change Symbol size of specific point

Posted by: marojevic on 8 August 2019, 10:53 pm EST

• 

  marojevic

  • Post Options:
  • Link
    Copy

  Posted 8 August 2019, 10:53 pm EST

  Hi,

  I’m using FlexChart’s itemFormatter to change the color of specific point.

  
  itemFormatterMap(engine, hitTestInfo, defaultFormat) {
      if (hitTestInfo.series.binding === 'WAY' && hitTestInfo.item.WellName === this.props.wellName) {
          engine.fill = 'DarkOrange';
          engine.stroke = 'DarkOrange';
      }
  
      defaultFormat();
  }
  
  

  And it works fine.
  
  http://prntscr.com/oqi2yy

  But when I try to change the size of the point by adding engine.strokeWidth, I get multiple points changed.

  
  itemFormatterMap(engine, hitTestInfo, defaultFormat) {
      if (hitTestInfo.series.binding === 'WAY' && hitTestInfo.item.WellName === this.props.wellName) {
          engine.fill = 'DarkOrange';
          engine.stroke = 'DarkOrange';
          engine.strokeWidth = 6;
      }
  
      defaultFormat();
  }
  
  

  http://prntscr.com/oqi461

  Not sure why is this happening, someone please help?

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 11 August 2019, 5:20 pm EST

  Hi,

  We were able to replicate the issue at our end so we have forwarded a bug report to the dev team with internal tracking id 393869. We will provide you with an update as soon as the issue is fixed.

  Regards,
  
  Ashwin

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 15 August 2019, 6:56 pm EST

  Hi,

  The issue is fixed in the latest nightly build. You may verify the same using the sample below:

  https://stackblitz.com/edit/react-kdye5b

  PS: The nightly builds are not passed through the QA cycle as all of our release builds do. Therefore, nightly builds are not suitable for the production environment.

  ~regards

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 19 September 2019, 5:59 pm EST

  Hi,

  The issue has been fixed in the latest stable build (5.20192.631). You may verify the same using the sample below:

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

  ~regards