Connect IQ 1.2.3 SDK Available!

Connect IQ SDK version 1.2.3 is now available for download! This is a small update to include support for the new quatix 3, and we decided to throw in a few updates and fixes while we were at it. :)

You can get it one of two ways:

Use the Connect IQ SDK Manager in Eclipse, by clicking the Connect IQ menu, selecting Open SDK Manager, and then clicking the Download button for Connect IQ SDK v1.2.3 released January 22, 2015.
Download directly from our developer site at http://developer.garmin.com/connect-iq/sdk/

General Changes:

Prevent sensor permissions from being selectable for watch-faces in Eclipse.
Update UX Guide page layouts graphics.
Update string format API documentation.
Fix case where a symbol was being added to the Rez.String module for each language defined.
Fix case where string routines would return an out-of-memory error instead of the actual error that occurred.
Fix an intermittent crash that occurred in certain applications over long periods of execution.
Fix memory leak that would occur when loading application settings.
Fix issue where application icons did not display correctly on Edge device in landscape mode.

Simulator Changes:

Properly blend fonts when running on 16-bit devices.
Update Tall Watch Icon Size to 40x33.
Update number fonts on the Edge 520 to match the device.
Correct 20pt number font on FR920XT.
Add quatix 3 device support, update D2 Bravo FW version.
Remove “suspend/resume app” from Simulator tool-bar as it is currently not functional.
Update Fenix 3 data field layouts to match recent firmware releases.
Better estimate application memory usage on OS X machines.

Known Issues:

If an Exception is thrown from a catch block, the finally block of the current try/catch/finally will not be executed.
The compiler is processing custom fonts in a way that allows for more data to be specified, but hand-made font files may display slightly different.

ruperthawkes over 9 years ago

SEE HERE - https://forums.garmin.com/showthread.php?341715-Font-rendering-bug-in-SDK-1-2-2-and-1-2-3

Any new of font rendering issues?

Having to fix one character, release new version, fix another character etc.

Is there a completely fail safe way to generate custom fonts that WORK!!? 1.2.2 AND 1.2.3 have made custom fonts completely unusable!

Former Member over 9 years ago

SEE HERE - https://forums.garmin.com/showthread.php?341715-Font-rendering-bug-in-SDK-1-2-2-and-1-2-3

Any new of font rendering issues?

Having to fix one character, release new version, fix another character etc.

Is there a completely fail safe way to generate custom fonts that WORK!!? 1.2.2 AND 1.2.3 have made custom fonts completely unusable!

Sharing your pain. Was able to overcome though. Export with "Force offsets to zero" bro and reduce padding, in some cases you will need to set negative padding in font file manually.

ruperthawkes over 9 years ago

X offsets are 0 , y offsets are 0, padding 0 - still rendering crap.

This is PURE guesswork, timely and causing lots of bad ratings. NOT HAPPY!

GARMIN, DO YOU CARE!?

Brandon.ConnectIQ over 9 years ago

@RUPERTHAWKES: We identified this in our beta testing (not so much a bug, just additional functionality with fonts that not all custom fonts were using), but it was resolved pretty easily by running fonts through BMFont and making adjustments to the offsets. From what I've seen over the past few days, it appears there's more of an issue than we understood.

You've already got a thread over here describing the trouble you're encountering, and I know some others have had similar issues. Let's try to keep the conversation limited to one thread, otherwise details could be lost as they're spread across multiple threads. :) What you've provided so far is very helpful, because it really details the exact trouble you're having. If you have any other examples, I'd appreciate whatever you're willing to provide. Otherwise, we'll investigate and see what needs a fix.

ruperthawkes over 9 years ago

Ta, will do!

Nikeow over 9 years ago

Comments about this new SDK from my limited testing.. (Previously using 1.2.1)

1) PRG size goes up. by a whopping 3kb
I did a whole bunch of work to save 2.5kB and then 1.2.3 eats them for lunch and dinner.

2) Without any changes in code, upon app exit, when I save the properties into object store, I get

Failed invoking <symbol>

Too Many Objects Error

  in storeUDValues (source/RFUD.mc:85)

  in myUD (source/RFView.mc:541)

  in onKey (source/RFView.mc:196)

  in handleEvent (D:\Projects\ciq-production\mbsimulator\submodules\technology\monkeybrains\virtual-machine\api\WatchUi.mb:364)

line 85 basically is trying to save a LONG (3 dimension) array of form

[0,1,3],
[0,2,3]...etc

this array is 36 long.

Former Member over 9 years ago

Getting the same error on Dictionary which exceeds 35 items. Please fix it asap.

Kyle.ConnectIQ over 9 years ago

NIKEOW and Vladimir, are these issues still happening in 1.2.4? We made some improvements in regards to these issues so they shouldn't be happening any longer. If they are, please reply and we'll take another look.

Nikeow over 9 years ago

Cursory look at 1.2.4 seems like the error didn't get spit out. But I'll have to confirm as I think I used a diff array of max 28 instead.

But the memory has gone down but still 0.5kb more than 1.2.1