Calling WatchUi.requestUpdate() does not always trigger onUpdate(dc)

According the documentation WatchUi.requestUpdate() shoud trigger onUpdate(dc) in a widget. When simulating my widget it does not always trigger this when calling the requestUpdate function from another function. Is this an issue or is this expected behavior. If it is expected, how should I work with this? The issue does not seem te be device related.

Using CIQ version 4.0.6.

0 jim_m_58 over 4 years ago

If you are doing this from a glance, on some devices where "live update=false", the Ui.requestUpdate will be ignored.

How are you seeing that onUpdate() isn't being called? Could it just be that the data isn't changing? Maybe add a println() call in onUpdate() to check.

0 jim_m_58 over 4 years ago

Do you have multiple views? Only onUpdate() in the top view will be called.

0 Mark_v_E over 4 years ago in reply to jim_m_58

This is being done from the View class.

I noticed, using break points, on the requestUpdate() and onUpdate(). When a requestUpdate() is called, the next step is not onUpdate() in every case.

0 Mark_v_E over 4 years ago in reply to jim_m_58

Multiple view classes? Not at the moment, there is only one view class.

0 jim_m_58 over 4 years ago in reply to Mark_v_E

onUpdate() won't be called next in every case depending on your app and what it does. Lest's say you got a timer running, callbacks for Sensor data, GPS data, and makeWebRequest, onUpdate might not be called until after one of the other callbacks is triggered.

Under what conditions are you calling requestUpdate(). Using breakpoints vs println calls can confuse things a bit. Let's say you have a timer running every second, but have a breakpoint set that takes a few seconds for you to respond to.

Also, which debugger? Eclipse or VS Code?

0 Mark_v_E over 4 years ago in reply to jim_m_58

I have a function that checks the output of a web request. When it has a unexpected result, I set some global string variables with a message and the fire onRequestUpdate(). The onUpdate function should process these strings and eventually display that to the screen.

I'm using VSCode.

0 jim_m_58 over 4 years ago in reply to Mark_v_E

The way I normally do something like this in in the callback for the makeWebRequest, do the Ui.requestUpdate(), as no matter what happened (good or bad) you want to show something on the display.

If it's not an "unexpected result", are you using a timer to call requestUpdate()? Remember that in a widget onUpdate is not called on a regular basis as happens with watch faces and data fields.

0 Mark_v_E over 4 years ago in reply to jim_m_58

I tried to do that. The check function is a sub call on the callback. When the sub function returns true it should do a requestUpdate, but it does not work always.

Is there a way do do this via a timer? Never thought about that actually.

0 jim_m_58 over 4 years ago in reply to Mark_v_E

In some of my widgets, all I do is create a timer and set it to fire every second (I do this in the view's initialize())

var timer= new Timer.Timer();
timer.start( method(:onTimer), 1000, true );

Then the onTimer() callback is just

function onTimer() {WatchUi.requestUpdate();}

With this, onUpdate() gets called every second.

Not sure why it's not working for you with the makeWebRequest call back. Post your callback function.

0 Yeti over 3 years ago

have you been able to solve it?
I have a similar issue: I'm reading a bit of data using Storage.getValue. that takes time. Would be cool to be able to show the user a progress bar.

What I've managed so far is to show a "loading" text on the first call of `onUpdate` and on the next call do the data reading.

But when I try to call periodically`requestUpdate` from the data reading function it just don't run `onUpdate` again.