this is caused by the view model used at the client side, which does not have a PropertyChangedNotify event. since there's no such event, the view doesn't know the value has been modified, so that that the view is not refreshed.
to solve this, a little refactor is applied: the event is added to the api models. see 928a17.
this is caused by the view model used at the client side, which does not have a PropertyChangedNotify event. since there's no such event, the view doesn't know the value has been modified, so that that the view is not refreshed.
to solve this, a little refactor is applied: the event is added to the api models. see 928a17.