Settings Menu and Data Fields

Former Member over 9 years ago

Hello,

I have a couple quick questions, did some searching and didn't find the answers I needed.

1) Is it possible for 3rd party apps to present their settings from the main settings area of the watch, as the built-in apps do?

For example, on my Vivoactive HR if I enter the menu from a default screen to get to the device settings, and go Settings > Apps > Run - I am able to set the app settings there, rather than having to launch the app and enter a menu.

2) Is it possible for menu items which are a boolean to present themselves as they do in the built-in menus (with a little switch rather than a sub-menu)?

3) Is it possible to have views/screens in your app which are built from user-configurable data fields as the native apps support?

For example, a page where the user can select 1-3 data fields of their own choosing to show within my app just as the built-in apps allow?

Essentially, I want my app to look / feel / behave as much like a built-in app as possible.

Thanks in advance.

travis.vitek over 9 years ago

1) Is it possible for 3rd party apps to present their settings from the main settings area of the watch, as the built-in apps do?

No. You can show settings inside the options for your widget/watch-app in response to user input (typically done in response to a menu key input).

2) Is it possible for menu items which are a boolean to present themselves as they do in the built-in menus (with a little switch rather than a sub-menu)?

Yes, but you have to code the menu yourself, and the appearance is device-specific.

3) Is it possible to have views/screens in your app which are built from user-configurable data fields as the native apps support?

Nope. Settings for data fields are only possible via Garmin Express or Garmin Connect Mobile at this time.

Travis

jim_m_58 over 9 years ago

With settings, I usually use app settings from GCM or GE. And you can do that while an app is running (see onSettingChanged() ) One thing it does is free up app memory, as you don't need much code in the app to do that. I think most time an app is set up the way the user wants, they don't change things that often - even with native apps, as on many watches they can just use a different profile if they want something different at times. (you may not want auto-pause if you're walking the dog, etc :) )

I do have a few cases where a couple things can be changed in the app itself without GCM/GE, and as Travis mentioned, usually tie them to the menu key. Examples are things like being choosing "hike" or "walk" before recording an activity, or using a black or white background (I figured that could change when your running the app based on sunrise, sunset, cloudiness, etc) But most cases, I don't want to lose the menu key for something that may not happen that often.