-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
loadMoreItems is called on ListViews items initialization #46
Comments
Generally loadMoreItems will be called when you scroll ListView to the bottom and when you do not have items you do not have scroll as well. |
+1 for this problem |
+1 Any solution for this problem? |
Hey @JuanDelgadillo In case you do not have initial items loaded you won't need loadMoreItem event. Instead just initialize your initial items collection. |
Did anyone come up with a viable solution for this? I am experiencing this issue too when I dynamically load in items. It loads <=10 items on the first go, then for what ever reason it loads more even though I did not scroll and am not anywhere near the bottom of the ListView. I'm taking a stab in the dark here but maybe it's an issue with the rendering of the list? Meaning if it renders each item one by one (which I don't know if it does), I guess at one point it would think it's near the bottom when the first one or two items are loaded? |
I confirmed that this is still an issue. If you have a very large array that you're loading from a service using paging (adding 10 items at a time and adding to the existing list on the client side), loadMoreItems is called continuously. |
+1, LoadMoreItems runs automatically whenever items are initiated. Which should not be the behaviour. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
From @qpautrat on April 20, 2015 9:6
Hi there,
Considering following code:
and this view:
I get:
However if my items is empty
loadMoreItems
is not called like it should be.Copied from original issue: NativeScript/cross-platform-modules#294
The text was updated successfully, but these errors were encountered: