Closed haideralifaizi closed 1 month ago
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
Thanks
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
Just released v 1.2.0 https://github.com/MPowerKit/VirtualizeListView/pull/14
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?