I'm currently using Infragistics v6.3 for Visual Studio 2003. I noticed that when I set the PageSize for the WebGrid to 10, the number of results for the first page is 10 (including the header). Which is fine, but when I click the 2nd page, I see only 7 rows. And when I click the 3rd page, I get 5 rows. Shouldn't it be consistent (except, obviously, for the last page, which may display less than 10 rows, depending on the total number of records) from page to page? In other words, I should see 10 rows on the first page, 10 rows on the 2nd page, and so on (excluding, of course, the last page)?
This is none of my business, but in my never-humble opinion, I would find that behavior unacceptably confusing. I'd be inclined to accept the cost of a doing a postback when the box is checked so that I could do my filtering at the datasource level and keep the number of visible rows constant.
Never mind, I figured it out.
There is a radio button control on the page that shows/hides rows based on the radio button selection. One button is labeled "Assigned to me," the other is labeled "Assigned to others." So, what's supposed to happen is that when I click "Assigned to me," some Javascript code is called to "hide" rows of data that are not assigned to me. If I select "Assigned to others," some Javascript code is called to "hide" rows that are assigned to me, but show rows of data assigned to others. It's the Javascript code that's interfering, because if I comment it out, it works perfectly fine. So, I'll have to figure this out. Thanks, anyway!
This is a quite weird behaviour. Are you sure that you are not modifying the PageSize property somewhere in code behind based on certain runtime criteria? Or, are you sure that the datasource itself changes (e.g. rows added or deleted implicitly in some way) before paging on and off?
I have created a very fast test with latest grid 2008.2 and tried some of the online samples, but frankly I have never seen this before and could not reproduce this locally.
So I guess I am either missing something or there is something in the setup the interferes with the grid. If you do not think this is the case, then I believe the best way to proceed would be to contact our official Developer Support department via this link:
http://devcenter.infragistics.com/Protected/SubmitSupportIssue.aspx
and let them know about the problem - maybe it is something that they are aware of, or something fixed, or something they can provide better ideas.