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
The ModelWrapper operates on the model instance that has been passed when calling the constructor. In some cases it would be great to be able to exchange the model isnance with a new one.
Example:
In a client server scenario the client shows a model instance loaded from the server. Later the client updates the model because other clients have changed the data by loading the data an creating a new model instance. To show the updated data we have two options at the moment:
Reload the view and reinitialize all bindings including the ModelWrapper.
Copy all data from the new model instance into the old one and call reload on the ModelWrapper instance.
It would be great when ModelWrapper would support the following third option:
3. call setModel and then reload on the ModelWrapper instance
The text was updated successfully, but these errors were encountered:
sideisra
pushed a commit
to sideisra/mvvmFX
that referenced
this issue
Apr 5, 2016
The ModelWrapper operates on the model instance that has been passed when calling the constructor. In some cases it would be great to be able to exchange the model isnance with a new one.
Example:
In a client server scenario the client shows a model instance loaded from the server. Later the client updates the model because other clients have changed the data by loading the data an creating a new model instance. To show the updated data we have two options at the moment:
reload
on the ModelWrapper instance.It would be great when ModelWrapper would support the following third option:
3. call
setModel
and thenreload
on the ModelWrapper instanceThe text was updated successfully, but these errors were encountered: