At Syncfusion, we are committed to fixing all validated defects (subject to technological feasibility andProduct Development Life Cycle) and including the defect fix in our subsequent weekly NuGet release which is scheduled on every Tuesday of the week and you can expect this fix on 23rd January 2019 weekly NuGet release. If you wish to receive this fix in a specific prior release product version please revert back to us(backwards compatibility subject to technological feasibility and our Support SLA) You can now track the current status of your request, review the proposed resolution timeline, and contact us for any further inquiries from the above link. We appreciate your patience until then.
CCCT CHANGJanuary 21, 2019 09:36 AM
Yeah, I have the same problem too. Look after for the next update : )
BKBharathiraja K Syncfusion Team January 22, 2019 04:29 AM
We regret for the inconvenience caused.
Due to the technical complexity of the issue, we are unable to include this fix in our 22nd January,2019 weekly NuGet. We will include this fix in our upcoming weekly NuGet release which is scheduled to be on 29th January 2019. We appreciate your patience until then.
NGNeil GuptaJanuary 22, 2019 09:28 AM
I'm having the same issue, waiting for the next update
BKBharathiraja K Syncfusion Team January 23, 2019 01:33 AM
Hi Neil Gupta,
We will update you once rolled out our weekly Nuget on 29th January 2019. Thanks for your patience until then.
BKBharathiraja K Syncfusion Team January 23, 2019 05:14 AM
Greetings from Syncfusion, we have tried to replicate the reported issue at our end by creating a simple sample, we are afraid that we are not able to reproduce the issue at our end. We have tested the below mentioned scenarios and used ObservableCollectiont to bind data.
1. Tested by removing data one by one and added new data dynamically using button click.
2. Tested by clear the data collection and adding new data dynamically.
3. Tested without setting any minimum and maximum value for the DateTimeAxis.
Since we are not aware of your exact application scenario, we were not able to reproduce this issue at our end, so can you please revert us by modifying the sample based on your application along with replication procedure. This will be helpful for us to investigate further and provide you a better solution at the earliest. And update the SfChart to latest version and check once whether the issue still reproduced.
BKBharathiraja K Syncfusion Team January 23, 2019 05:23 AM
Hi Neil Gupta,
We regret for the inconvenience caused. Since we have planned Volume-4 SP1 service pack release on coming 4th February and include all the fix in service pack, we will not release next weekly build which was planned to roll out 29th January. We appreciate your patience until then.
NGNeil GuptaFebruary 5, 2019 01:01 PM
I just downloaded the 188.8.131.52 nuget package, and the cropping issue is still there. Was the fix supposed to be in this release?
DRDhanasekar R Syncfusion Team February 6, 2019 10:59 PM
Hi Neil Gupta,
Due to technical difficulties, we were unable to include the fix in our SP1 release (184.108.40.206). But we have found workaround to resolve this issue in sample. We can resolve this issue in any one of the following ways.
1.Setting UseSafeArea to true in Content Page. Please refer following code snippet