Loose access to $scope about ng-websocket

[kumorig]

ng-websockets events doesn't trigger a angular $digest. (Which I really think it should, btw.). Anyway, all you have to do is trigger it yourself.

$scope.message = message;
$scope.apply(); 

This can potentially trigger an error if angular is already in a digesting state. One easy way to waif for the previous digest to complete is to use $timeout. (You have to inject it):

angular.module('bedappApp').controller('MainCtrl', function ($scope, $timeout, $websocket) {
    ...
    ws.$on('event', function (message) {
        $timeout(function(){
            $scope.message = message;
        });
    });

(Using $timeout without a delay-value will run a function immediately or as soon as the current digest finishes).

[jfranki]

I am new to AngularJS and this one was driving me nuts, I even looked everything there is to know about scopes and inheritance.

The solution of @kumorig works, but is missing the '$':

$scope.message = message;
$scope.$apply();

It really is a valid workaround, but it kind of "de-angularizes" the main purpose of websockets:

$apply() is used to execute an expression in angular from outside of the angular framework.

Is there another way of achieving this with ng-websocket or something that we are missing?