NgModel not properly synced/watched when using datetimepicker directive on input field about angular-eonasdan-datetimepicker HOT 5 CLOSED

@anx-ckreuzberger OK I think I have solved the reported problem in 0.3.8. Please check the update. I have updated the main plunker with both options: http://plnkr.co/edit/n8L8UZ?p=preview

@Tamadadoo I am not sure, but possibly the update also solves your problem. If you can, update the library in your project and please report back.

from angular-eonasdan-datetimepicker.

I started investigating it and it is worse than I thought. I will need some more time to fix this one.

from angular-eonasdan-datetimepicker.

I agree with the issue reporter, when for instance you have another version of the same date field (so same model ) for the purpose of displaying a "summary" tab in a big multi-tab form , then that second one does not listen/sync with the change in the model from the other. So generally speaking, change to the model which may come from somewhere else than the current ae-DTP field are just not observed. I was struggling to find a fix but for now I just resorted to some hack on my detailViewController to handle the refreshes, case by case (dirty).
Otherwise, thank you for the great contrib.

from angular-eonasdan-datetimepicker.

Indeed the revised $render and onchange did the trick ! And also allowed for a proper management of required inputs, when they are emptied. Many thanks. All for the better.
Out of curiosity, what did the deep watch of the options resolved ? what was the issue ? (the commit before)

from angular-eonasdan-datetimepicker.

@Tamadadoo #13

from angular-eonasdan-datetimepicker.