Watchface: Segment

Liking the looks :) but:
Fenix 3 with SW 8.20. Default watchface appears on the watch but when I attempt to change fields to different settings from my phone it doesn't work. also, changing to another watchface and trying to go back to this one results in the default watchface being displayed, in a broken way.

Liking the looks :) but:
Fenix 3 with SW 8.20. Default watchface appears on the watch but when I attempt to change fields to different settings from my phone it doesn't work. also, changing to another watchface and trying to go back to this one results in the default watchface being displayed, in a broken way.

Yes, a few people have mentioned this. It's very strange!
I have not been able to re-create it on 3 different devices (F3, VAHR, FR235).

Here's the watchface working on a Fenix 3 (8.20) and Vivoactive HR with latest firmware;
http://imgur.com/a/1E8Ek

Hmm. Do you have an Android device? What's your default language?

Thanks.

ftrimboli - there is a log on the watch which provides details of the crash in \garmin\apps\logs named ciq_log.txt.

If it's when settings are changed, check out point 10 in the new Developer FAQ #2:

https://forums.garmin.com/showthread.php?359183-New-Developer-FAQ-2

There's a long term issue where you might be expecting a "number" for a setting, but you might see a "float" instead, which can cause a crash, and there's a simple way to correct for that.

Yes, a few people have mentioned this. It's very strange!
I have not been able to re-create it on 3 different devices (F3, VAHR, FR235).

Here's the watchface working on a Fenix 3 (8.20) and Vivoactive HR with latest firmware;
http://imgur.com/a/1E8Ek

Hmm. Do you have an Android device? What's your default language?

Thanks.

Android device with 6.0, English. as I mentioned before: the default watchface displays fine for the first time it's installed. but changing display options has no effect on the watchface and it crashes if you attempt to change it to a different one and then back again.

There's a long term issue where you might be expecting a "number" for a setting, but you might see a "float" instead, which can cause a crash, and there's a simple way to correct for that.

Ah excellent - Jim, you truly are the master!

Yes, this was my next line of enquiry. Only seems to affect Android devices. I've updated the code with the suggested function, and submitted version 1.3 - would be great if any Android users could test this.
I have dozens of consumer electronics, with the exception of an Android phone :)

ftrimboli - no problem! Like I said, this has been a long time issue (since app settings was introduced in 1.2.0) and something that can be missed. It just takes a few lines of code to fix, and will be something that soon becomes common in your code.

working flawlessly now. thank you both guys.

if I may: is the extra space is reserved for future data fields? (alt etc), or could it be possible to make the fonts bigger to take advantage of the maximum space available? (probably custom graphics and a lot of work, right?)

working flawlessly now. thank you both guys.

if I may: is the extra space is reserved for future data fields? (alt etc), or could it be possible to make the fonts bigger to take advantage of the maximum space available? (probably custom graphics and a lot of work, right?)

Soon. I've actually drawn a larger font - and bluetooth, percent, and heart segments - here's it is in action on the simulator.

looking good :cool: the bigger the better :)