I've noticed in your code samples elsewhere that you also use Ext.apply() on an object's prototype, vs Ext.override() on an object's instance in your code sample above. Is this merely personal preference, or is there some reason behind it?
public function getTarget([String selector], [Number/String/HTMLElement/Element maxDepth], [Boolean returnEl])
* returnEl : Boolean
(optional) True to return a Ext.Element object instead of DOM node
Joris, false is not a valid selector. If you want an Ext.Element you will need to pass a valid selector. If you don't need the selector then like Animal posted, wrap it in an Ext.get or Ext.fly.
Jack Slocum
Ext JS Founder
Original author of Ext JS 1, 2 & 3.
Twitter: @jackslocum jack@extjs.com
I've noticed in your code samples elsewhere that you also use Ext.apply() on an object's prototype, vs Ext.override() on an object's instance in your code sample above. Is this merely personal preference, or is there some reason behind it?
There's no difference. Ext.override puts the properties from the 2nd arg into the 1st arg's prototype. Ext.apply puts the properties from the 2nd arg into the 1st arg, so you just specify ".prototype" on the 1st arg.
There's no difference. Ext.override puts the properties from the 2nd arg into the 1st arg's prototype. Ext.apply puts the properties from the 2nd arg into the 1st arg, so you just specify ".prototype" on the 1st arg.
i wanna one help. i have a grid with summary and pagination. My question is how to show the summary for all rows while pagination. If i change the next page of grid the summary shows only for that page. but i want summary for all rows.
Why are you posting this question is this really old thread?
ps. You would have to use a remote summary (e.g. your server returns the summary values and the grid summary shows that info instead of calculating it itself).
Originally Posted by mystix
Regards & Thank You
Reply With Quote
