You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, it is great that dgrid supports objects in the underlying store, which makes displaying more complex data really flexible.
I use this feature within an editor grid and wrote a custom widget to modify the object. But when triggering the onChange event of my custom widget, the grid does not recognize the changed value.
The reason is the compare statement in editor.js on line 53.
Replacing the statement as seen below, seems to fix this. I tested this with some widgets (DateTextBox, NumberSpinner, TextBox, FilteringSelect) and it worked fine.
Is there another reason for not using the simple compare operator I hadn't recognized?
First of all, it is great that dgrid supports objects in the underlying store, which makes displaying more complex data really flexible.
I use this feature within an editor grid and wrote a custom widget to modify the object. But when triggering the onChange event of my custom widget, the grid does not recognize the changed value.
The reason is the compare statement in editor.js on line 53.
Replacing the statement as seen below, seems to fix this. I tested this with some widgets (DateTextBox, NumberSpinner, TextBox, FilteringSelect) and it worked fine.
Is there another reason for not using the simple compare operator I hadn't recognized?
regards, Philipp
editor.js
The text was updated successfully, but these errors were encountered: