ac-change runs before model is updated?

[ghost]

ac-change seems to run before the model is updated.

Angular's ng-change runs after model update..

Doesn't it make sense to do the same as angular?

[ghost]

I've created a workaround for the problem. Don't know it is the most efficient but is works for what I need without changing too much =)

Add

"afterModelChange" :"&", 

to the scope of the directive.
Add a watch to the confirmedItem

$scope.$watch("confirmedItem.text", function () { 
                if ($scope.confirmedItem != null && $scope.confirmedItem.text != "" && typeof $scope.afterModelChange === 'function') {
                    $scope.afterModelChange();
                }
            }, true);

It makes this possible:

<ac-select after-model-change="DoYourThing()" ac-model="myModel" ac-options="item.ItemProperty for item in getItems()"></ac-select>

In the controller DoYourThing is called after model update, so $scope.myModel can be used in it.
$scope.myModel will contain the last selected item instead of the old one (which is the case with ac-change)