Hi.
We're finding that e-value isn't behaving as you'd expect ng-model to behave on the number spinner, which is causing us problems.
I've attached a demo project to demonstrate.
In the demo I've binded one number spinner using ng-model and the other with e-value.
The ng-model spinner acts on changes with ng-change, and the e-value spinner uses e-change.
When you change the values of the spinners, they behave differently.
When the change events output the entire binded object (eg. itemsForNgChange or itemsForEChange) to the log, they both output the latest data (eg. the value displayed in the UI).
However, if the change events output a variable within the binded object, behavior differs.
- ng-change displays the up to date data (what you see in the UI).
- e-change displays the previous version (what you saw in the UI prior to the change).
And if you change the value again, the same happens again (e-change is always one change behind).
This is causing us problems when acting on the data.
Are we implementing it incorrectly, or is this a bug?
Cheers.
Attachment:
ejnumbertextboxdemo_3d27a55e.zip
