Yes, of cause! But I think that it's better to use (p.rowID != null)
Hello Tony,
you are right. It's better to use
It's very good news! Thank you! I will test the code later. If I would find a problem I will post it you.
Best regards
Oleg
Hello prince!
Look at my old answer on very close question on the stackoverflow. I think it's what you need.
Best regards
Oleg
Hi Slawek,
dynamical
Hi!
You should use data option of jqGrid and create the grid with all the data in one operation. Usage of addRowData is slower bacause it insert the data in the grid row after the row. Every inserting of the row follows recalculation of position of all other exsiting element on the page or at least to reflow (see here for more details).
Usage of data
@mohsen: Look at the demo which is small modification of the early demo from the answer. It shows how to implement custom searching control (stype: “custom”). Another answer could help you in the next step ot the implementation if you would need to implement interval searching locally.
Best regards
Oleg
By the way Tony, the discussion about the subject you can read here. In my tests introduction of two loops instead of one loop brought no performance decreasing. The first loop fill read input data with respect of $.jgrid.getAccessor and save results in the object rd. The second loop read the properties from rd, call addCell and save results in rowData.
Regards
Oleg
Hello Tony,
the which you currently published on github contains one loop where addCell just contails additional parameter rd. The problem is that rd is not yet full filled. It contains only the named properties of the previous columns and contains no information about next columns. I can't imagine, that one can solve the problem without deviding the corresponding loop in two loops like I described before.
Additionally I think that one have to adjust the code of addRowData too in the place where folmatCol will be called (about here).
Best regards
Oleg
P.S. I wanted remind you Tony about another my previous suggestion. If you find the time could you take a look at it.
In my opinion the problem with different format of rawObject is common problem of custom formatters, cellattr and rowattr. It could be easy solved by dividing
I suppose that the problem exist because old data values will be not removed by
jQuery("#myJqGrid").jqGrid('setGridParam', { data: data });
The above code works good with empty data, but it could worrk wrong if another (old) data already exist. What you can do is setting the data array using getGridParam:
var referenceToInternalData = jQuery("#myJqGrid").jqGrid("getGridParam", "data");
referenceToInternalData
You will find the answer here and here. In another answer you
Sorry Tony, but in both: my suggestion and your implementation there are bugs. The correct line of code should be
p = $.extend(true, {}, $.jgrid.jqModal || {}, p);
The currect code (see here)
p = $.extend(true, $.jgrid.jqModal || {}, p);
changes the value of $.jgrid.jqModal on every execution of createModal function with the value of p parameter. Moreover, the currect code of navGrid
Copyright 2014 TriRand LtdAll Rights ReservedRSS
Back to Top