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
A declare([ Memory, Trackable]) object does not automatically update the grid.
When dstore/Memory#setData is called on a declare([ Memory, Trackable]) object, the grid is not updated. In order to update the grid a reference to the grid must be available (#refresh()) or the dojo/store/Memory#putSync method must be used.
In comparison, dojo/store/Memory#setData does update the associated dijit/form/Select object.
Should dstore/Memory#setData be made to update its associated grids?
The text was updated successfully, but these errors were encountered:
This certainly seems to make sense on the surface. However, dgrid has always behaved this way, even the 0.3 releases that used Dojo object stores, so changing behavior at this point would be a breaking change. There may be other considerations as well.
A declare([ Memory, Trackable]) object does not automatically update the grid.
When dstore/Memory#setData is called on a declare([ Memory, Trackable]) object, the grid is not updated. In order to update the grid a reference to the grid must be available (#refresh()) or the dojo/store/Memory#putSync method must be used.
In comparison, dojo/store/Memory#setData does update the associated dijit/form/Select object.
Should dstore/Memory#setData be made to update its associated grids?
The text was updated successfully, but these errors were encountered: