How to avoid proxy of Parent Grid Panel?

[livinglegends]

Hi,

In my application I have two grid panel. GP1 and GP2.

In GP1, I am using proxy and hitting url of server. GP2 extend GP1 and in GP2, I don't want any proxy as data of GP2 are not coming from server.

Now, when I click on any column of GP2 it fires server url of GP1 (call proxy of GP1). How to avoid proxy of GP1 when I do sorting on GP2

[livinglegends]

Actually scenario is different. It is not due to proxy.

But, in parent grid (GP1), I have implemented one function say doSorting on 'sortchange' event.

So, in GP2, it is also calling parent's doSorting method.

I have overridden that method in GP2 but it has stopped grid level (client side) sorting also.

How, to prevent default behavior of grid sorting and prevent parent method calling?

Hope, I am cleared.

thanks

[Condor]

GP1 and GP2 should not be using the same store.

GP2 clearly doesn't need a proxy and should be remoteSort:false, so it needs it's own store.

[livinglegends]

GP1 and GP2 should not be using the same store.

GP2 clearly doesn't need a proxy and should be remoteSort:false, so it needs it's own store.

Yes...both Grid Panel has their own store. I am not using same. But still problem exist and in GP2 I have set remoteSort:false also.

[Condor]

How did you define G1 and G2?

[livinglegends]

How did you define G1 and G2?

Refer below code snippets..

App.G1 = Ext.extend(Ext.GridPanel, {
 ........
........
// define store here for G1........
........
});

App.G2 = Ext.extend(App.G1, {
 ........
........
 // define store here for G2........
 ........
});

[Condor]

You can't define a store in the prototype! You need to create the store in the constructor or initComponent.

[livinglegends]

Yes...I did same thing...
In init method of each grid, I have defined store like below (dont go on syntax, its just pseudo code...)

initComponent:function() {

           ..........
           ..........
           this.store = new Ext.data.JsonStore({
                fields : fields,
                data: {"data":[]},
                autoLoad : false,
                remoteSort : false
            });
           ..........
           ..........
}

[Condor]

Ah, exactly what I don't like about initComponent!

This code in G2 will create a store, next it calls the G1 superclass initComponent that overrides the store with it's own store.

This wouldn't have happend when you would have applied the store to the config object in the constructor.

[livinglegends]

Ah, exactly what I don't like about initComponent!

This code in G2 will create a store, next it calls the G1 superclass initComponent that overrides the store with it's own store.

This wouldn't have happend when you would have applied the store to the config object in the constructor.

So, what is better way? plz provide some code hint..