Chartrow issues

[Tom]

Hello, I've encountered multiple issues regarding a chart containing multiple chartrows. Attached is a sample to be used as reference.

Requirements: 

• There should always be a red chartrow border visible between multiple chartrows
• There should always be a yellow vertical annotation which overlaps all chartrows.

Issue 1: Run the sample. Check the Price checkbox, then check the Price2 checkbox. Two chartrows appear, but the red chartrow border is missing, even though it's defined in the sfChartEx class line 174.

https://postimg.cc/mcbtwmhw

Issue 2: Run the sample. Check the Price checkbox, then check the Price2 checkbox, then uncheck the Price checkbox. The vertical gridlines are cut in half.

https://postimg.cc/7fKH4qLg

Issue 3:  Run the sample. Check the Price checkbox, then check the Price2 checkbox, then uncheck the Price checkbox, then check the Price checkbox, then uncheck the Price2 checkbox. Default labels and vertical gridlines appear, meaning an additional default axis has been erroneously created.

https://postimg.cc/Ff9x2tTk

A workaround for all these issues is to completely recreate the chart every time a change happens, but I would like to use a better solution. How can these issues be resolved?

Thank you.

Attachment: sfChartRows_635f1983.rar

[Suyamburaja Jayakumar]

Hi Tom, 

 

Greetings from Syncfusion. 

 

Currently we are validating the reported issue and we will update the complete status on or before April 13, 2020. 

 

Regards, 

Suyamburaja J 

[Suyamburaja Jayakumar]

Hi Tom, 

     

We were able to reproduce the reported issue 1 & 2 at our end and confirming these as bug, still we need to validate Query 3 and we will update the complete status by tomorrow April 14, 2020.  

 

Regards, 

Suyamburaja J. 

[Hemalatha Marikumar]

Hi Tom, 

 

Thanks for your patience. 

 

We have confirmed these as bug and you can now track the status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.    

 

https://www.syncfusion.com/feedback/13468/gridlines-and-row-customisation-are-not-properly-updated-when-dynamically-change 

 

 

The fix will be included in our Volume 1 SP1 2020 release which is expected to be rolled by first week of May 2020. We appreciate your patience until then.   

  

Note: The provided feedback link is private, and you need to login to view this feedback. 

 

Regards, 

Hemalatha M. 

 

 

[Tom]

Great, looking forwards to the fix.

[Suyamburaja Jayakumar]

Hi Tom,  

 

As promised earlier, I will surely move this fix into upcoming Volume 1 SP1 release. 

 

We appreciate your patience until then. 

 

Regards, 

Suyamburaja J. 

[Suyamburaja Jayakumar]

Hi Tom, 

 

Sorry for the miscommunication. 

 

We have checked it further and found that it has been resolved through sample level. Since you have added the axes in the axis collection manually for every series Y axis which is not required that will be automatically added in the axis collection if initialized in the Series Y axis.  

 

Also, we have to initialize the primary and secondary axis for overriding default axis which will be displayed automatically when initialize the chart. 

 

Please find the modified sample attached with it 

Sample link: https://www.syncfusion.com/downloads/support/directtrac/general/ze/sfChartRows1027725209  

 

Please let us know if you need any further assistance.      

  

Regards,  

Suyamburaja J.  

[Tom]

Thank you, so in sfChart the axes are added and removed automatically when the series are added or removed. However, now a new problem has cropped up with your modified sample: Run your sample, check the Price checkbox, then the Price2 checkbox, then uncheck the Price2 checkbox. A red chartrow border is visible in the middle of the chart. Now, uncheck the Price checkbox. The border is still visible. How can the chartrow borders be correctly updated?

[Suyamburaja Jayakumar]

Hi Tom, 

 

Thanks for your patience. 

 

The requested scenario is reproduced for us, we are validating the scenario in both source and sample level. we will update the complete details on or before 28, April 2020. 

 

Please let us know if you need any further assistance.      

  

Regards,  

Suyamburaja J.  

[Suyamburaja Jayakumar]

Hi Tom,  

  

Sorry for the delay.  

 

We are confirmed that reported issue as a bug and currently we are working on this issue at our end. The issue will be fixed and included in our Volume 1 Service Pack 1 release which is expected to be rolled out by Mid of May 2020. We appreciate your patience until then.    

 

Please let us know if you need any further assistance.   

 

Regards,  

Suyamburaja J. 

 

[Tom]

Hi, I've run this sample with the 18.1.0.52 version but it seems the fix for this issue was not included. What's the status for this issue?

[Hemalatha Marikumar]

Hi Tom, 

 

Sorry for the continuous delay on moving this fix.  

 

Since having last minute breaking issue, we have stopped to include this fix. Currently we have ensured and fixed the same even completing all possible testing case. The complete fix is included in our tomorrow rolled out weekly NuGet release. We appreciate your patience and please ensure the same with tomorrow rolled out weekly NuGet release version.  

 

Regards,
Hemalatha M. 

[Tom]

I've tested the 18.1.0.53 Nuget release, and it works. Thank you, Hemalatha.

[Hemalatha Marikumar]

Hi Tom, 

We are glad to hear that the reported issue resolved.

Please let us know if you need any further assistance.

Regards,
Hemalatha M.