I have defined a ListView declaritively like this:
<ul data-role="listview" data-bind="source: myDataSource" data-template="myTemplate" data-bound="displayEmptyText" data-endless-scroll="true">
</ul>
The displayEmptyText function checks the number of data items in the DataSource and displays "No items available" if there are 0 items. This works when I set endless-scroll to false but doesn't fire the event when endless-scroll is true.
Is this going to be fixed in a coming release? Is there a better way to achieve the display of the "No items available" message?
Cheers
Dean
4 Answers, 1 is accepted
Rank 1
The data binding process of the listview widget is a bit different when virtual mode is enabled - indeed this is not documented well enough. A good place to perform this check would be in the datasource change event handler.
Regards,Petyo
Telerik
Rank 1
A general comment about this:
If a list view with endless scrolling is going to continue to be so different, and break many of the normal list view's features, it really should be a separate widget. The amount of things that just don't work when endless scrolling is set to true is very frustrating.
you are spot on with this. This was our initial design direction. However, the ListView already supported (albeit incorrectly) endless scrolling and press to load more. Introducing another widget with the same features working in a different way would be even more confusing.
Unfortunately, the databound event has a special role when the widget is MVVM bound. Triggering that when scrolling would cause a significant performance penalty (as all DOM elements would be re-iterated). I do understand that this results in a certain level of inconsistency – this is purely due to implementation details which we can't change without causing big breaking changes in the current behavior.
Petyo
Telerik