How to prevent a widget to revert to the watch page after 59 seconds

Does anybody know if it is possible to prevent the watch to automatically revert from a widget to the standard watch face after 59 seconds?

I have a timer where I like to sound the alarm after the specified time, but unfortunately when the watch reverts to the standard face, then the timer is reset.

I have asked for a timer that would work even when the widget is not active - here - but alternately it would be good if you could prevent a widget to revert automatically to the standard watch face.

jim_m_58 over 10 years ago

I think it would be easier to do from the mobile device that gives you a keyboard, and I don't get how persistence in the object store works yet (or how to use it), and this isn't something you'd want the user to define more than once, as the API key is a string of about 16 random characters, with letters and numbers. For the WS ID itself, there is a json call to WU that will return stations near a GPS location, but if you have a WU station, you already know it's call sign and don't need a list of those in the area (that could actually be a long list in some places)

travis.vitek over 10 years ago

The object store is just the functions getProperty() and setProperty() on the app object. You can store primitive types, including arrays and maps, using those functions. All you'd need to do is have a menu that allowed the user to enter the API key, and then store the provided key using setProperty(). The user would only need to do this once. You might even want to prompt them for the API key if one isn't found when the application starts.

Once you have the API key stored, before making a request to the weather service, you would retrieve the key using getProperty() and adding that key to the URL.

Travis

jim_m_58 over 10 years ago

This is stuff that even the author of the code wouldn't want to enter on a 1" screen (and for new folks, this would be their first exposure to the widget). so until a user can set stuff in the object store using CIQ, there is no point in using an object store for this widget, IMHO.

And using the original topic of this thread, I would hold back anyway until it can reliably get data with time to actually see it, before it reverts to the watchface. (10 seconds on the vivoactive).