You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
at first, thank you for creating this plugin, it will help us a lot for our project.
After playing around with the plugin for a while, I have some trouble when initializing the pager.
I try to dynamically fill the pager with content that is getting loaded from the server, but the content gets visible only when navigating to another page and back.
exports.vmMain = observableModule.fromObject({
selectedIndex: 0,
items: new observableArrayModule.ObservableArray(),
loadStoryChapters: function () {
var self = this;
ffHttpModule.startHttpRequest(
...
//success callback
function(response) {
self.set("items", new observableArrayModule.ObservableArray(response.listItems));
//does not work correctly, title and text are visible after navigating to another page and back
self.get('items').setItem(
0,
{ id: "..." title: "First item", text: "This is the text of the first item..." }
);
}
);
}
});
When using this code for a ListView, the data is shown as expected, so the source of this problem really seems to be somewhere in the pager implementation.
I hope this can be fixed.
The text was updated successfully, but these errors were encountered:
pager not updating the page after response
i have a activity indicator which will run on ngOninit and when i get the response i just remove the activityIndicator with ngIf but the pager not updating the page
Hello,
at first, thank you for creating this plugin, it will help us a lot for our project.
After playing around with the plugin for a while, I have some trouble when initializing the pager.
I try to dynamically fill the pager with content that is getting loaded from the server, but the content gets visible only when navigating to another page and back.
Here is what I am doing:
When using this code for a ListView, the data is shown as expected, so the source of this problem really seems to be somewhere in the pager implementation.
I hope this can be fixed.
The text was updated successfully, but these errors were encountered: