SfListView swipe resets itself when SfChart element is update in DataTemplate on Android

[Rui Silva]

Hi,

I have a SfListView with swipe. It also has a DataTemplate that contains a SfChart that has a binding with data that is being updated each second.

All works well on UWP but on Android when I try to swipe to any side, after a second it resets itself, closing the swipe panel.

In the attached solution is possible to see what I'm trying to say.

Attachment: Swiping_with_chart_b15d47ca.zip

[Muthu Kumaran Gnanavinayagam]

Hi Rui, 

 

Sorry for the inconvenience. 

 

We have confirmed that "Swiped item gets reset in AutoFitMode" is a defect and we have logged a bug report for the same. The fix for this issue will be available from our 2018 volume 1 main release. 

 

Regards, 

G.Muthu kumaran. 

[Rui Silva]

Hi,

Where is the bug report so I can track that?

Is there any workaround for this?

I'm thinking of manually assign the height through events and calculations. Is this the right way?

I have to ship a release in February so I don't know if the 2018 volume 1 main release comes in time for this fix.

Thanks!

[Ashwini Paranthaman]

Hi Rui, 

Yes, we can understand your concern. 

Please inform your Enterprise Admin to update your profile with the current Essential Studio version details you are using. Else please check with our sales team to have multiple portal.  This will help us to create incident to provide fix for your issue. 

Regards, 

Ashwini P. 

[Rui Silva]

Hi Rui, 

Yes, we can understand your concern. 

Please inform your Enterprise Admin to update your profile with the current Essential Studio version details you are using. Else please check with our sales team to have multiple portal.  This will help us to create incident to provide fix for your issue. 

Regards, 

Ashwini P. 

Hi,

I believe that my profile is already updated to the latest version as of now (15.4.0.20)

Can you try again?
If it still can't, please provide more details on how to do the required changes.

Thanks

[Vinoth Kumar Perumal]

Hi Rui Silva,

 

The version (15.4.0.20) is updated in your profile. But, the incident will be created based on the version which is selected by your portal admin. Since, your portal admin set the version (13.1.0.21) of DevScope portal.

 

As per the record, you are the Power User of the portal. You can’t edit the product version of the enterprise portal. Only, admin can change the product version for your project.

 

Please follow the provided steps in the article, it will help to update the product version in the project

 

https://www.syncfusion.com/kb/8048/how-to-change-the-enterprise-portal-product-version

 

Once you updated the latest product version, the incident created with that version and then our team will provide the Patch for the reported issue.

 

 

Regards,

Vinoth Kumar Perumal

[Gangabharathy Murugasen]

Sent: Thursday, January 18, 2018 6:38 AM
 

Let me tell you this is the best way to spend useless time on support emails back and forward. That “requirement” of setting a version number in the admin portal is a ridiculous excuse. And then recreate the case????. No added value to Syncfusion or the customer, maybe a metric hack for the support personnel, but a really bad “Service Design” that will simply drive customers unsatisfied.  

Pure bureaucracy. Sorry! 

[Rui Silva]

Hi Rui Silva,

 

The version (15.4.0.20) is updated in your profile. But, the incident will be created based on the version which is selected by your portal admin. Since, your portal admin set the version (13.1.0.21) of DevScope portal.

 

As per the record, you are the Power User of the portal. You can’t edit the product version of the enterprise portal. Only, admin can change the product version for your project.

 

Please follow the provided steps in the article, it will help to update the product version in the project

 

https://www.syncfusion.com/kb/8048/how-to-change-the-enterprise-portal-product-version

 

Once you updated the latest product version, the incident created with that version and then our team will provide the Patch for the reported issue.

 

 

Regards,

Vinoth Kumar Perumal

Sincerely, I don't understand why the portal needs to be attached to a version when we have teams that use different versions and can need support on any version no matter what the version is configured in the portal by the admin.
This bureaucracy is cumbersome and it is a bad model when it comes to support. Our admins shouldn't be bothered to make this type of change that, by the way, works half of the times.

Your portal needs to be agnostic to this and when creating incidents we should access any version on the selection that is in the creation form (if you create a incident for us, you should only ask which version we are using beforehand).

Either way, please check if the version is right this time and create the incident.

Thank you.

[Ashwini Paranthaman]

Hi Rui, 

We are sorry for the inconvenience. 

We have forwarded your request to Management and they will get back to you regarding the same. We have created an incident under your account to track the status of the issue. Please follow up the same for further updates. 

Regards, 

Ashwini P. 

[Florian]

Hi Rui, 

 

Sorry for the inconvenience. 

 

We have confirmed that "Swiped item gets reset in AutoFitMode" is a defect and we have logged a bug report for the same. The fix for this issue will be available from our 2018 volume 1 main release. 

 

Regards, 

G.Muthu kumaran. 

Any updated on that? I have installed version 16.2.0.46 on my Xamarin.Forms project, but the bug not seems to be resolved.

[Rawoof Sharief Muthuja Sherif]

 

Hi Florian,  

  

Sorry for the inconvenience. 

 

When the SfListView is in AutoFitMode and if the layout of each ViewCell item gets refreshed at runtime, we have reset the SwipeOffset for the swiped item and re-layout the items which are in the View. 

  

Please find the behavior of SfListView in AutoFitMode when the contents inside its ItemTemplate is updated at runtime.  

  

• In Android platform, we have internally force layout the SfListView when its content gets modified.
•  In iOS platform you need to manually force layout the SfListView to resize its contents. Because, we are unable to find out child view’s size changes from parent view as per Xamarin iOS framework architecture. Hence we have introduced a new method ForceUpdateItemSize in SfListView to force the update the item size in iOS platform when its content size is affected. You need to call that method when making changes at runtime.
• In UWP platform we have force layout the SfListView only when the scroller comes into View or when its ‘y’ position changes.

  

We have tried to overcome this behavior and so we have logged a defect in our source. But as it breaks the actual behavior of SfListView while updating the content size at runtime, we could not proceed by resolving the reported query. Sorry for the inconvenience.  

  

Regards,  

Rawoof M.