System.exist() for widget?

Hi guys,

for an app I have a nice feature that allows it to long press the "back" button to exit the app immediately, regardless of the navigation depth. The same feature does not work for widgets, as the "exit" method seems to not do anything. Is there a reason behind that? Requested behavior should be that the method takes the user back to the watch face, so basically the same that happened after the timeout of a widget.

Thanks!

Bye

Top Replies

subra over 3 years ago in reply to Travis.ConnectIQ +1

Travis.ConnectIQ said:
I don't believe that we'll be revisiting.

Then I suggest it's a good idea to at least mention in the API docs that System.exit() doesn't work for widgets.

developer…

All Replies

Former Member over 5 years ago in reply to jim_m_58

Hi jim,
Thanks for you reply. You can test by yourself the widget, the timeout appears after 25 minutes on the VA3.
I don't have the problem on the FR945 and the fenix 5

As I said, the problem here, is that after the timeout (on the VA3) the watchface is reset to the system clock...

jim_m_58 over 5 years ago in reply to Former Member

What firmware are you running?

jim_m_58 over 5 years ago in reply to jim_m_58

I installed your widget on a va3, and I get attemp 1,2,3,4, then connection failure and it times out in 40 seconds and returns to the watchface and for me, a CIQ one..

Former Member over 5 years ago in reply to jim_m_58

Thanks for having test - and sorry for the delay of my answer, I wasn't notified
You need to be connected to Internet via your smartphone to make it works...

I am not sure what you mean by CIQ one ?

I have maybe an explanation for the time out :

Every 1 sec I test the backlight and reactivate it.

static function generalTimerCallback(){
//put the backlight on
if (Attention has :backlight) {
Attention.backlight(true);
}

}

firmware 7.2

jim_m_58 over 5 years ago in reply to Former Member

After the timeout, when I return to the watch face, I return to the CIQ WF I have active. You said you returned to a system one,. Turning on the backlight shouldn't impact the timeout.

Former Member over 5 years ago in reply to jim_m_58

Did you test it when your Ikigai was connected ?

The timeout is maybe alterate because I switch automatically the view every 3 seconds. After the fourth view, it returns to the first view (automatically).

The bug appears only on the VA3 (from my tests - I only have and tested a FR945, a fenix5 and a VA3)

jim_m_58 over 5 years ago in reply to Former Member

I was connected to a phone, but the widget never connected. Switching views should not reset the timeout in any case. Only user interaction should.

Former Member over 5 years ago in reply to jim_m_58

Ok, thanks for you reply.

I'll do some more tests to see where is the problem and what interfers with the timeout.

jim_m_58 over 5 years ago in reply to Former Member

Have you tried other widgets from the store? Do they time out? What FW is on your va3?

subra over 3 years ago in reply to Travis.ConnectIQ

Travis.ConnectIQ said:
I don't believe that we'll be revisiting.

Then I suggest it's a good idea to at least mention in the API docs that System.exit() doesn't work for widgets.

developer.garmin.com/.../System.html

I also struggled with this unusual behavior because it's common in most programming languages that exit terminates a process.