my second example/ code is the more complicated version and not the simplest way - that what I meant in the previous post saying (actually the best way is to use the URL of the picture directly ) . In same cases you can try to load an url which is not directly visible for you widget and you need to load it e.g. via $http or fetch services first to memory and then set to the source prop
In your case you can use the simple way (which do the same but internally for the widget implemented)
In your case you can use some code like this:
$scope.setWidgetProp("3DImage-1","src", "app/resources/Uploaded/pinger_tap.png");
or
var global_count_int1=0;
//----- HERE IS THE ANIMATION from Server
$interval( function(){
{
if( global_count_int1 > 9) global_count_int1=0;
global_count_int1++;
var url_source= "app/resources/Uploaded/pic_0"+global_count_int1+".gif";
$scope.$applyAsync(function() {
//$scope.view.wdg['3DImage-3']['source'] =url_source; //direct assigment to the prop
$scope.app.params['image_url']=url_source;//assignee to app par + binding
}
); //end applyAsync
}
} , 500);
The second function will show in loop every 0.5 seconds a other picture - from pic_01.gif to pic_09.gif and again....
In this case the function will change a value of a parameter which has binding to the resource property of the 3DImage (src). Using a application parameter in same case will update the display more stable as the direct assignment of the property.