In a paging grid, when filters are added the result is a useless grid: it shows as many pages as initially but all of them are empty but those that have a row that matches the pattern. This is useless from the usability point of view.
What I think it should do is group all rows that match the pattern of the filter an then paginate those rows.
In fact, I think the right way to implement this is by adding the filtering information in the loading system just as you do with the sorting. This way the server-side could do the filtering so the client did not have to do that effort.
It is to say, add a field in a class that extends from ListLoadConfig that has the filtering information, just as you have for the 2.x version (FilterPagingLoadConfig)
icfantv: The generics issue should be better in beta3 - give that a try, see if that helps.
paucarre: can you post a simple entrypoint that is wiring up the paging/filtering and drawing blank pages - the example at http://sencha.com/examples-dev/#Exam...motefiltergrid seems to be doing this, though there are only two pages, filtering a column reduces it to one column. An example you can offer demonstrating this issue would be helpful for us.