Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugs after updation Mpowerkit.virtualizelisview to 1.1.7 #13

Closed
haideralifaizi opened this issue Jul 19, 2024 · 4 comments
Closed

Bugs after updation Mpowerkit.virtualizelisview to 1.1.7 #13

haideralifaizi opened this issue Jul 19, 2024 · 4 comments

Comments

@haideralifaizi
Copy link

haideralifaizi commented Jul 19, 2024

I have updated to latest version 1.1.7 but list becomes laggy and also not smooth. Also, one more thing that when i update element of the list, there are wrong elements show. Then, I upgrade down to 1.1.6 version, it becomes very fast as always everything scrolling, etc. Can you fix that issues that in 1.1.7 version because scrolling becomes slow, crash on updation of whole item and many bugs?

@Alex-Dobrynin
Copy link
Contributor

Alex-Dobrynin commented Jul 20, 2024

yes, use 1.1.6 for now, I will mark 1.1.7 as deprecated. working on this issue already, happens only on android

it is very complicated issue, because it should properly work for all cases. previous implementation worked badly with lists of entries, where user can type text #5

And thus i cannot use Translation X/Y for android, I have only one way is to change physical position of the item, not virtual as Translation is. And therefore the performance on android will be worse as it was before, sorry but this is the victim.

And I'm trying to make as less remeasuring layout calls as I can. but this is how MAUI is implemented

@haideralifaizi
Copy link
Author

Thanks

@Alex-Dobrynin
Copy link
Contributor

Ok, so for this issue I have to completely redesign render engine and it can take some time. I've already did some investigations and pushed them to separate branch, but I have to reject previous render of the items, that was just as changing items translation (which is virtual change) to view.Arrange() at least for android

@Alex-Dobrynin
Copy link
Contributor

Just released v 1.2.0 #14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants