Calculated Timer Losing time if view is switched to another DF

I have a DF which I would like to keep track of the time stopped.

when the data field is in the foreground, the DF works great. When Speed is less than 1meter per second, it would start counting the seconds (+1000) increments. All is Good.

However, once I move to another Data Screen (eg: Move from Screen 1 to Screen 2) essentially the timer stops counting the seconds (despite the speed still being < 1mps)

How can I get this timer to continue incrementing under these conditions:

1) The Data Screen has been changed such that Data Screen 1 is no longer in the foreground

2) The timer continues to increment as long as the Speed is still < 1mps

basically, a background process that acitively monitors the GPS Speed and increment a timer counter. (Is using background process the only way? https://developer.garmin.com/index.php/blog/post/guest-post-creating-a-connect-iq-background-service)

jim_m_58 over 7 years ago

onUpdate() is only called when the DF is visible. Are you doing this there?

compute() is called if the DF is being displayed or not, and would be the place to do this.

Nikeow over 7 years ago in reply to jim_m_58

Thanks Jim.. putting it into compute() works.

I didn't know the distinction of compute being called regardless of the DF is in foreground or otherwise.

jim_m_58 over 7 years ago in reply to Nikeow

Yes. And another thing is onUpdate() can be called multiple times if you have the same DF more than once on the same screen. You'll see that in the sim with 2 or more DF layouts.