-
30 Jan 2008 4:29 AM #21
Add deferredRender:false to your CardLayout config.
Jozef Sakalos, aka Saki
A lot of valuable info at:
Saki's Extensions and Plugins
Saki's Extensions and Plugins Docs
Saki's Examples, Latest: Grid in Card Layout
Saki's Blog, Featured: Writing a Big Application in Ext, Latest: Grid MultiSearch Plugin Video
-
30 Jan 2008 5:27 AM #22
no this did not help... It seems there is an bug when rendering Comboxes etc. in the body-Element of an Card.
When add the card later the input field is displayed:
[B]Won
-
30 Jan 2008 8:13 AM #23
Try to replace deferedRender:false with deferredRender:false.
Jozef Sakalos, aka Saki
A lot of valuable info at:
Saki's Extensions and Plugins
Saki's Extensions and Plugins Docs
Saki's Examples, Latest: Grid in Card Layout
Saki's Blog, Featured: Writing a Big Application in Ext, Latest: Grid MultiSearch Plugin Video
-
30 Jan 2008 8:30 AM #24
oops... ok, i change it but it will only work when add the card later. When i rendered directly in the card-body the combo will not displayed.
This must be a problem with comboxes and card-layout...
-
30 Jan 2008 8:32 AM #25
Yeah, can be. There were some threads on this problem; maybe it's worth to search.
Jozef Sakalos, aka Saki
A lot of valuable info at:
Saki's Extensions and Plugins
Saki's Extensions and Plugins Docs
Saki's Examples, Latest: Grid in Card Layout
Saki's Blog, Featured: Writing a Big Application in Ext, Latest: Grid MultiSearch Plugin Video
-
31 Jan 2008 12:18 PM #26
Hi, thanx for sharing this great plugin.
I had problem with search over data in grid when the searching data were in own store linked by id (eg. ComboBox).
So I made this little correction (for local only) and works for me:
andCode:. . ,onTriggerSearch:function() { var val = this.field.getValue(); var store = this.grid.store; var cm = this.grid.getColumnModel(); // help array with [dataIndex][columnIndex] var cmfield = new Array(); for(ix = 0; ix < cm.getColumnCount(); ix++){ cmfield[cm.getDataIndex(ix)] = ix; } . .
Code:. . this.menu.items.each(function(item) { if(!item.checked || retval) { return; } var rv = r.get(item.dataIndex); var c = cm.getColumnById(cmfield[item.dataIndex]); if(c && c.editor && c.editor.getValue()==="" ) { var cr = c.editor.field.store.getAt(c.editor.field.store.find(c.editor.field.valueField,rv)); if(cr) { // it may be undefined - not assigned value rv = cr.get(c.editor.field.displayField); } } rv = rv instanceof Date ? rv.format(this.dateFormat || r.fields.get(item.dataIndex).dateFormat) : rv; . .
-
31 Jan 2008 4:53 PM #27
Thank you for improvement. I'll test it a bit and then I'll include it in the main code provided there are no problems. Remind me in a couple of days.
Jozef Sakalos, aka Saki
A lot of valuable info at:
Saki's Extensions and Plugins
Saki's Extensions and Plugins Docs
Saki's Examples, Latest: Grid in Card Layout
Saki's Blog, Featured: Writing a Big Application in Ext, Latest: Grid MultiSearch Plugin Video
-
3 Feb 2008 12:44 PM #28
Using the plugin remotely
Using the plugin remotely
Sorry guys, but this might be a silly question, I am new to Ext. I am trying to use the plugin to search data remotely rather than local on a paging grid. I am wondering how do I get access to the field's value so I can pass it in the params object in the call dataStore.load({params:{start:0, limit:25}});
Thanks in advance. Great Plugin!
-
3 Feb 2008 12:58 PM #29
You don't need to do it. It's handled by the plugin itself; you just type the text, click search trigger and the request is sent to server. You can use Firebug to see what is sent to server.
Jozef Sakalos, aka Saki
A lot of valuable info at:
Saki's Extensions and Plugins
Saki's Extensions and Plugins Docs
Saki's Examples, Latest: Grid in Card Layout
Saki's Blog, Featured: Writing a Big Application in Ext, Latest: Grid MultiSearch Plugin Video
-
3 Feb 2008 1:09 PM #30
Wouldn't it be better to use renderers in these cases? I can imagine an option "searchUsingRenderer" where you wouldn't care about how data is really stored but you'd search values returned by renderers.
Also, in the code you posted, there can be an error if you use some special fields with editors that do not have stores. I'm not therefore incorporating it to the main code what I'd do with a cleanly coded searchUsingRenderer option.
Jozef Sakalos, aka Saki
A lot of valuable info at:
Saki's Extensions and Plugins
Saki's Extensions and Plugins Docs
Saki's Examples, Latest: Grid in Card Layout
Saki's Blog, Featured: Writing a Big Application in Ext, Latest: Grid MultiSearch Plugin Video


Reply With Quote