I am unable to understand the behavior of PagingMemoryProxy in EXTJS 3.4. a. It is defined as follows:
proxy:new Ext.ux.data.PagingMemoryProxy(jsonData),
listeners : {
load : {
scope : this,
fn : function(actorStore) {
var r = actorStore.getRange();
var modified = actorStore.getModifiedRecords();
for ( var i = 0; i < modified.length; i++) {
for (j = 0; j < r.length; j++) {
if (r[j].get('plannedResourceId') == modified[i].get('plannedResourceId')) {
var changes = modified[i].getChanges();
for (p in changes) {
if (changes.hasOwnProperty(p)) {
r[j].set(p, changes[p]);
}}}}}}}}
So, the problem what i encountered was when i delete a row using:
gridPanelToRefresh.getStore().removeAt(value.value.rowIndex);
After performing this above mentioned task, when i click on refresh button at that time, the deleted data comes in the grid too. I mean the store which was created using the proxy mentioned above is not getting refreshed.
Can you please suggest some solutions for the same. One lead i got on the same is getModifiedRecords() does not gets the deleted records.