Panning reversed axis would result invalid chart

Panning reversed axis would result invalid chart

Posted by: Yifan_Zhang on 12 June 2020, 2:46 am EST

• 

  Yifan_Zhang

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 12 June 2020, 2:46 am EST

  When axis is reversed, the panning interaction will render invalid chart with no axis labels. See the example in https://www.grapecity.com/wijmo/demos/Chart/Features/ZoomingAndPanning/purejs
  
  Adding the “reversed: true” to X axis and panning, the chart would become invalid. Please help resolve this issue. Thanks.

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 15 June 2020, 12:41 am EST

  Hi Yifan,

  We are sorry for the inconvenience caused. We have forwarded this issue to the dev team with internal tracking id 440978. We will update you once this issue is fixed.

  Regards,
  
  Ashwin

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 28 July 2020, 4:13 am EST

  Hi Yifan,

  The issue has been fixed in the latest nightly build of Wijmo. You may verify the same using the sample link below:

  https://stackblitz.com/edit/js-qtud4a

  This fix will be included in the next stable release.

  PS: Nightly builds have not passed through the QA cycles as all of our release builds do. So, it is not recommended to use nightly builds in production.

  ~regards

• 

  Yifan_Zhang

  • Post Options:
  • Link
    Copy

  Posted 28 July 2020, 1:21 pm EST

  Thanks for the fix. Can’t wait for the next stable release!

• 

  Yifan_Zhang

  • Post Options:
  • Link
    Copy

  Posted 30 September 2020, 1:44 am EST

  Hi, I found another issue from the sample. It lost the capability of restricting the axis original bounds (min/max). Previously, it will not be able to be panned over min/max, now there are no bounds for panning. Could you take a look?

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 1 October 2020, 2:15 am EST

  Hi Yifan,

  I have replied to your query on SupportOne at the link below:

  https://supportone.componentone.com/casedetail/465888

  For reference, I am posting the response here:

  Thanks for reporting the issue, I have forwarded this to the developers with internal tracking id 466030. I will update you once I will hear from them.

  Regards,
  
  Ashwin

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 22 December 2020, 7:59 am EST

  Hi Yifan,

  The issue has been fixed in the latest nightly build of Wijmo. You can verify the same using the sample link below:

  https://stackblitz.com/edit/js-c2ao6y

  Note that nightly builds have not been passed through the QA cycles and are not suitable for production environment.

  ~regards