I copied the .SET file to my watch SETTINGS folder, but still I can't customize the setting in the watch, it only appears the Apply button when I search the app in the Watch's Watch…
Make sure you have the latest version of the Eclipse Plugin (1.2.1), and then under the "Connect IQ" menu in Eclipse, there is the "App Settings Editor".
No way to test right now on the deal devices when sideloading.
You can test the settings on a real device, you just can't test setting them. You can set the proper values in the simulator and then copy the settings file from the simulator (%Temp%\Garmin\Apps\SETTINGS\) to your device.
As Teun said, you can copy the .set files from the simulator to a real device so see how they look and function. Forgot about that!
But in the simulator, you should check that your "onSettingsChanged()" code works as expected, as you can't test changing stuff with a side-load.
On a real device with an app from the store (like a watchface), you can use GCM to change stuff, and those changes should be reflected in that watchface very soon (a second or two) after you hit "done" in GCM.
You can test the settings on a real device, you just can't test setting them. You can set the proper values in the simulator and then copy the settings file from the simulator (%Temp%\Garmin\Apps\SETTINGS\) to your device.
WHAT????!!!1111? No, tell me its a joke.
Why I can't just copy file to watch and test changes from GCM?
To be honest, the easiest thing to do it upload it to the app store, but mark it as a beta app (it's on the first screen where you have the iq file and the version). You can then use your phone to change settings, and not generate a new .set file for anything you want to try.
Yeah it's been changed on both Windows and macOS since that post.
Windows: %TMP%\com.garmin.connectiq\GARMIN
macOS: $TMPDIR/com.garmin.connectiq/GARMIN
(If you use a very old SDK, it may still use the old tmp dir which lacks the com.garmin.connectiq path component, but newer SDKs def user the newer paths.)
FlowState, thanks for sharing the paths to the GARMIN folder. However the .SET file copy approach didn't work for me.
I ran the command $TMPDIR/com.garmin.connectiq/GARMIN/APPS/SETTINGS, and that yielded the following path: /var/folders/3_/890c6v6x33g1mwn1tnsywp500000gn/T/com.garmin.connectiq/GARMIN/APPS/SETTINGS
I copied the .SET file to my watch SETTINGS folder, but still I can't customize the setting in the watch, it only appears the Apply button when I search the app in the Watch's Watch Faces menu. Other installed ones from Connect IQ do have the customize option.
So, I think I'll give it a try to jim_m_58's approach, releasing a beta version to test app settings.
I copied the .SET file to my watch SETTINGS folder, but still I can't customize the setting in the watch, it only appears the Apply button when I search the app in the Watch's Watch Faces menu. Other installed ones from Connect IQ do have the customize option.
To be clear, there's two types of settings:
1) the type of settings that this thread is talking about, which are available for all CIQ devices, are defined in resource property/settings .XML, and exist in a .SET file in GARMIN/APPS/SETTINGS. These settings are accessed using the Connect IQ app (for iOS or Android) or Garmin Express (PC or Mac). They are not accessed from the device itself.
2) "on-device settings" (not available for data fields and watch faces on older devices). This the type of settings that you're thinking of when you talk about Connect IQ watch faces that allow settings to be changed on the watch itself.
On-device settings are available for CIQ data fields and watch faces, since CIQ API level 3.2.0. For other app types - widgets and device apps - devs have always been able to implement their own settings UI without any special support from the framework. Data fields and watch faces need special support for on-device settings bc they have very limited / nonexistent user input capabilities, and they lack the ability to push a new view which would allow for full user input.
Device applications, widgets, and audio content providers all accept user input that allow them to implement on-device settings in the app. Watch faces and data fields are not allowed to accept input or push views that would allow on device configuration.
Watch face configuration is available to the user in the system Watch Face menu. Data field configuration is available from the activity menu.
It's not a bad idea to release a beta version, as it will allow you to test your settings in the Connect IQ app. But it won't allow you to change settings on the watch itself.
