CIQ 3.2 - Wow!

Just installed 3.2 (see https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/connect-iq-3-2-now-available),

and in looking at the change log in the SDK README file, a bunch of new features!

Time to start trying stuff!

Top Replies

PlayItLoud over 4 years ago +4
Same code. One running Connect IQ 3.2... Guess which one

Just added this at the top of my onUpdate(dc) method:
```
if(dc has :setAntiAlias) {
    dc.setAntiAlias(true);
}
```
xuxumatu over 4 years ago +1

ERA is no starting
PlayItLoud over 4 years ago +1

NICE! Watch faces and data fields can now have user-configurable on-device settings with settings views.

All Replies

jim_m_58 over 4 years ago

The Analog sample in the3.2 SDK has an example of on device settings. It's triggered in the sim under Settings>Trigger App Settings.

Former Member over 4 years ago in reply to jim_m_58

jim_m_58 said:
The Analog sample in the3.2 SDK has an example of on device settings. It's triggered in the sim under Settings>Trigger App Settings.

Thanks Jim! I was looking for this!

Former Member over 4 years ago in reply to jim_m_58

jim_m_58 said:
The Analog sample in the3.2 SDK has an example of on device settings. It's triggered in the sim under Settings>Trigger App Settings.

Do the on device settings have to be unique from the settings accessible in the mobile app? Is it possible to have the same settings in both places (for older and newer devices)? Also, is there a good tutorial or link that shows how to retrieve on device settings to implement in code? The Analog sample shows how to make the settings menu, but I did not see where the settings are actually applied in the app.

jim_m_58 over 4 years ago in reply to Former Member

It doesn't look like they are used in the WF itself, but the stuff from the settings is in Application.Storage, so could easily be accessed in a WF. And I think instead of Application.Storage, Application.Properties could be used, so you could change the same stuff with on-device or with app-settings

TheMagician over 4 years ago in reply to jim_m_58

AppBase. getSettingsView() why does Garmin generate these settings view from the settings.xml file automatically like in the connect app?

jim_m_58 over 4 years ago in reply to TheMagician

No. You build it yourself. You can have on watch settings without having app-settings (no settings.xml). See the Analog sample in the SDK.

jim_m_58 over 4 years ago in reply to jim_m_58

One thing to keep in mind, is on device settings will increase the memory needed for a watch face. If you're currently using 91kb out of 92kb max in one, it may not be a good candidate to try this on.

TheMagician over 4 years ago in reply to jim_m_58

Every good watch face will always have both options. Settings in the app and all the same settings inside the device.

TheMagician over 4 years ago in reply to TheMagician

The anti alias feature ist just crap for such low resolution device displays. Everything looks blurred and not crisp and sharp enough. Just my thoughts, sorry. A color fade within a polygon or rectangle would be nice. ;-)

TheMagician over 4 years ago in reply to TheMagician

The Analog sample for the watch face on device settings is horrible. A menu inside the menu to open the watch face settings... not really user friendly, sorry.

I've implemented a direct watch face menu2, to figure out how much the memory increase it will be...

Multilanguage support is already included but only to toggle boolean values.

https://apps.garmin.com/en-US/apps/2851d38b-22a8-41b6-84bf-2b0d4a229869

The trouble starts by exiting the settings... but a solution is already working within the implementation (the simulator of the 3.2.1 is very buggy in this scenario and doesn't behave like the watch).

Have fun to test it out.