Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Calling SaveViewModelAsync() twice #1226
If I use the CancelViewModelAsync() Method, the ViewModel doesn't get the PropertyChanged of the Model anymore. So if I edit the ViewModel again, the changes will be written to the Model, but changes on other Properties will not be shown in the ViewModel.
Steps to reproduce
Done in this TestRepo: https://github.com/RCP161/IDataObjectTest/tree/master/M1Vm2
=> The TextBlock does not change the state anymore. You can trace the problem in the output window.
=> Nothing happened.
The ViewModel should still listen on the PropertyChanged of the Model.
ViewModel dosen't listen to the PropertyChanged of the Model anymore.
You don’t have to do this as default.
Or what is the common scenario for this? Have I to change the view after calling cancel or save?