fix(multiple): setViewValue compatible with 1.3-rc.1+

[dimirc]

Demo plunker

Closes #191
Closes #176

[LeleDev]

Seems OK for me

[dimirc]

@dimirc Thanks for helping solve this.

While that solution in #193 will fix the primary issue, it has a side effect where it will run all the setViewValue code paths twice including parsing, validation, and calling any ng-change listeners with an empty string before calling w/ the correct value.

While thats not necessarily a terrible thing, it feels a bit like a hack solution to me. I'll try to get a PR going when I get a bit of spare time! :)

@mpolichette I'm trying a different approach to avoid calling twice setViewValue and yet parse model correctly

[zyadsherif]

Thanks for the solution the model is now updating yet I needed to hook on the ng-change directive for the model and now it fires twice, first with an empty model then with the correct changed value.

Any ideas how to solve this issue?