Dear Tony,

I thank you enormous, as Italians say: sei grande 🙂 (I am not Italian though, I still say it)

—
sledge

PS: I had to rewrite your patch into without .namedItem referenced, since it didn't work initially. Maybe it had conflicted with my custom changes to grid.base.js . If others will complain about still not working 3.4.4, let me know in this thread.

Subgrid as grid.

Have got to revert back old version

Hello, Tony and all,

Here is my contribution to the project: the working inline edit editrules validation. It colors the non-validating input text controls with pink color and alerts with the list of errors. Once alert dismissed, it focuses the caret onto the first erroneous control.
It does not proceed to post until all errors are corrected.

Enjoy and welcome any feedback. (note the commented info_dialog, due to such visualizing, the .focus() does not work afterwards).

I will improve it to validate also other type of controls (i.e. select :)) when my boss asks for it hehe 🙂

*** /.../jqGrid-3.3.1/js/grid.inlinedit.js

Soo, are you rewriting it/will be rewriting it, or can I take a peep?

—
sledge

To add more information in the matter, which is a major blocker for me..:

I have tried even swapping grid with its subgrid – same results (Loading forever).

It would appear that it breaks on the bigger JSON data being somehow invalid. But it consists only from 10 elementary not-corrupted strings (for 10 columns) — that's for the subgrid. (remember — the same code generates the json from the DB query). Main grid contains 3 columns only.

If I replace subgrid with hardcoded xmlstring, everything shows ok. jsonstring meanwhile cannot be shown.

Is there a problem with many-columned json strings?

Probably — no, because the biggest mistery in this was that JSON data with 10 values was displayed OK, when the subgrid was still hardcoded in the .html file. Once I have refactoried it to be eval()`ed, it stopped showing data.

Well, I hope I'll break through this one..

Standing by, pals,

—
sledge