Simulator stops after making web request

First widget ever.

When a web request is done and after the callback function finishes, the simulation just stops. The onUpdate functions runs no more and it looks like there is nothing else happening. Am I missing something in my callback function? or is it the way I handle the data receved the problem? Or maybe is a configuration issue? Here is the code:

module myModule
{
    var _response;
	var RequestInProgress = false;
	
    public function  request(rest_method,type,id,headers,body)
		{
			if (RequestInProgress)
			{
				return 0;
			}
			var updateCallback = new Lang.Method(myModule, :onReceive);
			
            //Stuff...
		  
		  Communications.makeWebRequest(url,body,options,updateCallback);
		  RequestInProgress = true;
		  
		  return 0;
		}
    public function onReceive (responseCode,data)
		{
			RequestInProgress = false;
			if (responseCode == 200)
			{
				_response = data.get("data");
			}
			else
			{
				System.println("Error " + responseCode);
			}
		}
}

I know the request works because I can print in console the reponse during the onRecieve function. I bet is something really obvious but I can't find it.

Top Replies

jim_m_58 over 3 years ago +1 verified

You probably want to do a WatchUi.requestUpdate() in the makeWebRequest() callback so that onUpdate() will be called. In a widget or device app, onUpdate isn't called on a regular basis as is the case…

All Replies

+1 jim_m_58 over 3 years ago

You probably want to do a WatchUi.requestUpdate() in the makeWebRequest() callback so that onUpdate() will be called. In a widget or device app, onUpdate isn't called on a regular basis as is the case for a watch face.

0 9635560 over 3 years ago

Also: are you testing in VSCode or Eclipse?
VSCode is still a bit shaky around the edges and I find it often loses console connection with the debugger. So I tend to code in VSCode and simulate using Eclipse.

0 8763879 over 3 years ago in reply to jim_m_58

Yes! that's it! Now It works as expected. Thanks a lot!
Is the update in widgets just slower than watch faces or the update must be always requested?

0 jim_m_58 over 3 years ago in reply to 8763879

in a widget or device app you must request it. In some it can be done by way of something like a callback as you see here where it's basic on something specific, in others, you set up a timer and use it's callback so it happens on a regular basis, say every second

0 jim_m_58 over 3 years ago in reply to jim_m_58

Here's a simple example of using a timer - in this case the timer fires every second so onUpdate() gets called every second.

    function initialize() {
        View.initialize();
        
		var timer= new Timer.Timer();
		timer.start( method(:onTimer), 1000, true ); 
    }
    
    function onTimer() {WatchUi.requestUpdate();}

0 8763879 over 3 years ago in reply to 9635560

I'm working on eclipse only I didn't know VSCode could be used. Thanks for the tip.

0 8763879 over 3 years ago in reply to jim_m_58

That is useful to know, thanks for the information and the example.

0 jim_m_58 over 3 years ago in reply to 8763879

One thing to note, and another reason to use a timer, is that on devices like the Edge devices, widgets don't time out. So you may want do do something like do your makeWebRequest every "x" minutes.

And for devices with CIQ 4.0 (Venu2/Venu2s), there are no longer "widgets", but instead "super apps" (it's behind the scenes when you build for a ciq 4.x device. If there is a glance view, you'll see it in glances and the widget will time out, but you'll also see it in the list of activities, and if started from there, it won't time out.