Note that there are some explanatory texts on larger screens.

plurals
  1. POextjs4 grid - changing column editor per row basis
    primarykey
    data
    text
    <p>ExtJS4 grid anticipates appropriate editor (cellEditor or rowEditor) per column. If a column's header field is dateField - date selector will be applied on every row in that column.</p> <p>What I need is an editor with different field editors per row, not per column.</p> <p>The Extjs3 solution is provided <a href="http://joekuan.wordpress.com/2011/03/22/changing-columns-editor-dynamically-in-extjs-roweditor/" rel="nofollow">here</a> - unfortunately doesn't fit in Extjs4 case. (please check that link to see explanatory images, cause I can't post images yet)</p> <p>There's also a single column solution called <a href="http://dev.sencha.com/deploy/ext-4.0.2a/examples/grid/property.html" rel="nofollow">property grid</a>, but again - it supports only one column and is very deviated from the standard Ext.grid component</p> <p>I have tried manually changing grid editor by customizing column.field and reloading grid.editingPlugin.editor, but always get a blank rowEditor panel with no fields.</p> <pre><code>//by default rowEditor applies textField to all cells - I'm trying to force custom numberFiled on apropriate row var numberField=Ext.form.field.Number(); grid.columns[0].field=numberField; //destroy current rowEditor's instance delete grid.editingPlugin.editor; //now, upon doubleClick on apropriate cell it should reinitialize itself (initEditor()) - and it does, but is an empty panel </code></pre> <p>what am I missing here? once I delete editingPlugin.editor everything should start from the beginning like during the first time rowEditor is called, but it looses all the fields</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload