2 reports of "not working" on 920xt

[warmsound]

Reported by users Hannu and Hugo Ojeda. Latter user on 1.5.3, including #16 fix.

Debug version of Crystal.prg, built for 920xt, attached, with debug.xml.
Archive.zip

Works in simulator. Suspected missing null check for ActivityMonitor.info field, but would like to confirm.

[warmsound]

James Nguyen reports that there is no apparent crash (no CIQ_LOG.TXT generated), but only goal meters and move bar appear - nothing else on screen. This suggests a font problem.

[warmsound]

Issue has been reported to Garmin here:
https://forums.garmin.com/forum/developers/connect-iq/connect-iq-bug-reports/1346637-custom-fonts-not-rendering-on-920xt-watch-simulator-ok

[warmsound]

Hey warmsound,

I took a look at the code on GitHub and it looks like you've been exposed to a bug that we have seen here before. This is a device specific bug on the 920XT. I could not find the forum posts where we talked about it, but the 920Xt cannot properly render custom font resources using antialiasing. A popular workaround for this issue is to create a custom fonts.xml that only the 920XT uses. This can be defined in Junges, as a totally other font resource or, but creating a resources-920xt folder to house the resources specific to that device. Make sure to turn off antialiasing for that device and the fonts should display without issue. I apologize that this is not as well documented/it is as difficult as it is to track down bugs in the forums.

Thanks,

• Coleman

[warmsound]

Non-antialiased font resources created for fr920xt: new resources-fr920xt folder, with own fonts/fonts.xml and symlinked fonts.

Merged to master in commit 3da1d7c.

Will check with James following release.

[warmsound]

There have been no further reports of issues on fr920xt since the above fix, so closing this issue.