paging toolbar?

Wow, this works great! but it doesn't seem to update the paging toolbar. I have used this extension to add in memory paging of datasets down to 20 rows per page. When loading 1000+ rows It correctly shows only the first 20 but the paging toolbar says page 1 of 1. When I manually type in page '2' and hit enter then the paging toolbar seems to "come alive" and correctly shows my second page of data. It also tells me that I now have 51 (in my case) pages of data. Is there some way to refresh the paging system to make this work as expected?

suntoast; that looks exactly like my example for locales in Ext 1.0.
For that i wrote up my own in memory paging proxy; guess there not many different ways to solve this, so we ended up with almost identical code

Take a look at it in the Ext 1.0 release: Ext-1.0/examples/locale/multi-lang.html and js. This one is currently a undocumented example that includes what i called a PagingMemoryProxy and it does the same thing

Hopefully i will have a full example of this with sorting and paging ready to be officially in the documentation for the 1.1 release if our benevolent dictator for life agrees to it

I tried the PagingMemoryProxy. It's cool. But I'm going back to HttpProxy()...

Reason is I find the ds hard to manipulate, especially when adding new row or deleting rows.

In particular, ds.reload() doesn't do anything. Maybe I missed something.

I think you nailed it, sorting also only applies to the displayed data. Using HttpProxy does increase the load on the server in a way (call to the server on almost every click), but for now it's a more perfect solution to me than PagingMemoryProxy.

yeah nice report, only a typo and common mistake (for me), not too bad

Should the Number of pages be updated in the PagingToolbar with the results returned (i.e. If the filter returns 1 row should the page count be 1 of 1)?

absolutly right; the filtering should modify the totalRecords attribute, at the end of filtering there should be this:
result.totalRecords = result.records.length;

If the filtered results span multiple pages, how do I see the other pages? Once I click on the next arrow the display no longer uses the filter and just displays the original data.

Did you put the filtering parameters in store.baseParams ?
baseParams will remember your filter settings, params given as a attributes to the load() method will not.
or use store.on('beforeload') event as covered elsewhere in the forums