Does calling onUpdate too frequently result in it blocking other functions or button presses like from delegates from working?

I have an app that works 100% well on the simulator, however, on the physical watch the routing function seems to prevent delegate calls from being initiated while it’s running, the function has to call onUpdate a lot to avoid triggering the watchdog in order to iterate through all the coordinates data.

I’m wondering if it is this that prevents delegate calls from being initiated until after the function is completed as I notice while the function was running the button on my vivoactive 3 did not trigger the app to exit until the function completed.

0 jim_m_58 over 1 year ago

CIQ is single threaded so the delegate won't run until your other function is complete

0 Scarecrow123 over 1 year ago in reply to jim_m_58

Interesting, so is there no way to interrupt a function?

0 jim_m_58 over 1 year ago in reply to Scarecrow123

When something like your onUpdate or a timer call back runs, it runs until completion or until the watchdog terminates your app.

If you are doing a bunch of math, you may want to use a timer callback itself to do the work and not do it in onUpdate by way of WatchUi.requestUpdate() as actually updating the display takes both time and battery

0 Scarecrow123 over 1 year ago in reply to jim_m_58

Does using a timer reset the watchdog then?

0 jim_m_58 over 1 year ago in reply to Scarecrow123

When the timer callback ends the watchdog is reset so the next time the callback runs it's a new watchdog

0 Scarecrow123 over 1 year ago in reply to jim_m_58

ah I always thought it was just onUpdate that reset it.