Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The "Loading..." which is not disappear means typically that an exception occur during of the filling of the grid or executing some callback functions like <code>loadComplete</code>. In you case the error was that you use <code>jQuery("#listU05").jqGrid.setColProp</code> instead of <code>jQuery("#listU05").setColProp</code> or <code>jQuery("#listU05").jqGrid('setColProp', ...</code>.</p> <p>You can use the code of <code>loadComplete</code> to</p> <pre class="lang-js prettyprint-override"><code>loadComplete: function(data) { $(this).jqGrid('setColProp', 'Thema', { stype: 'select', searchoptions: { value:"a:a;b:b" } }); } </code></pre> <p>I recommend you additionally to consider to use <code>beforeProcessing</code> for such operations. In case of setting searching properties of <code>colModel</code> it is not really important, but if you want use <a href="http://www.trirand.com/jqgridwiki/doku.php?id=wiki%3apredefined_formatter#formatter_type_select" rel="nofollow">formatter:'select'</a> and load the <code>editoptions.value</code> from the server then usage of <code>beforeProcessing</code> is exactly correct place. The data returned from the server are not yet processed. So you can change <code>value</code> property of <a href="http://www.trirand.com/jqgridwiki/doku.php?id=wiki%3acommon_rules#editoptions" rel="nofollow">editoptions</a> and <strong>already during the current processing of the data</strong> the <code>value</code> property of <a href="http://www.trirand.com/jqgridwiki/doku.php?id=wiki%3acommon_rules#editoptions" rel="nofollow">editoptions</a> will be used by <code>'select'</code> formatter.</p>
    singulars
    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.
    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