Hi don't know if this is a bug, but it costed my a lot of frustration :D In the end I solved it but I just wanted to share and check.
Anyway I had a timepicker MVVM bound to a value. On a certain JS event i would assign that timpickers value, but not by going through the viewModel object, rather directly using the value method of the picker. That would cause the timepicker to lose sync with the MVVM model and its value would go to a null... I didn't realise what was the bug for a good 5 hours of frustration and trying to get it to work :D.
I don't know if going like this is something I should do. I guess If I'm using MVVM I should alawys edit values through the model, but the situation was specific and the expected reaction was for it to work the other way around.
Anyway I had a timepicker MVVM bound to a value. On a certain JS event i would assign that timpickers value, but not by going through the viewModel object, rather directly using the value method of the picker. That would cause the timepicker to lose sync with the MVVM model and its value would go to a null... I didn't realise what was the bug for a good 5 hours of frustration and trying to get it to work :D.
I don't know if going like this is something I should do. I guess If I'm using MVVM I should alawys edit values through the model, but the situation was specific and the expected reaction was for it to work the other way around.