Now, I know by design RadDataPager is implimented to work the way it is for my scenario (described below), but I am wondering how to work around it.
I am using ASP.NET AJAX... I saw a suggestion for Silverlihgt RadDataPager to use some sort of RadDataPager.PagedSourse.PageIndexChanged or something maybe.
My Scenario:
I understand that this is the way it's suppose to work, as it's really meant for a User to do something like going to last page, and then filtering items (since the item collection would chage Telerik assumes the RadDataPager should take the User to the first Page).
So is there a good way to do what I want and prevent TotalRowRequest from firing PageIndexChanged with a PageIndex of zero?
Thanks for your time to read and reply!
-Dan
I am using ASP.NET AJAX... I saw a suggestion for Silverlihgt RadDataPager to use some sort of RadDataPager.PagedSourse.PageIndexChanged or something maybe.
My Scenario:
- I am binding a RadDataPager using the TotalRowCountRequest event.
- I start by binding the RadDataPager (PageSize=5) to have a TotalRowCount of 10 (item count of a collection I'm keeping in ViewState).
- User clicks to view Page #2 (which means PageIndex 1) <-------------- so far so good
- User deletes one of the items in my ViewState item collection.
- Now the TotalRowCountRequest gets the updated count (which is now 9 because the User removed 1 from the original 10)
- PageIndexChanged is now fired with a NewPageIndex of 0 <------------------ this is what I want to prevent
- Now the TotalRowCountRequest gets the updated count (which is now 9 because the User removed 1 from the original 10)
I understand that this is the way it's suppose to work, as it's really meant for a User to do something like going to last page, and then filtering items (since the item collection would chage Telerik assumes the RadDataPager should take the User to the first Page).
So is there a good way to do what I want and prevent TotalRowRequest from firing PageIndexChanged with a PageIndex of zero?
Thanks for your time to read and reply!
-Dan