Connect IQ 1.2.5 SDK Available!

I'm a little late on this announcement, but still want to point out: Connect IQ SDK version 1.2.5 is now available for download!

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.5 released February 18, 2016.
  • Download directly from our developer site at http://developer.garmin.com/connect-iq/sdk/

General Changes:
  • Add documentation for Custom Drawables to the programmer’s guide.
  • Update Input sample to be compatible with the Tall Watch screen type.
  • Fix application icon overriding bug.
  • Fix out-of-memory error when allocating large objects (such as parsing large JSON responses).
  • Fix a bug in custom font generation where xoffset was incorrectly used to determine width versus position within the glyph itself.

Simulator Changes:
  • Add vívoactive HR device and update Tall Watch with final fonts, memory sizes and data-field parameters.
  • Reduce Simulator run-time system memory usage.

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.
  • For the new Fenix 3 HR: are heart rate (current or resting) and/or intensity minutes available for watchfaces?
  • Former Member
    Former Member over 9 years ago
    For the new Fenix 3 HR: are heart rate (current or resting) and/or intensity minutes available for watchfaces?


    I was wondering the same thing and have looked through the docs but it does not appear they have exposed those for watch faces.
  • I simply want to draw a bitmap using dc.drawBitmap(5, 35, dagR). But for that string simulator says invalid resource in onUpdate....

    It works fine in CIQ SDK 1.2.1 but not in 1.2.4 and 1.2.5. Then what I missed between these versions? What changed that prevents drawing the bitmap?
  • Have you tried building and running the primates sample program? I draws a bitmap just like you are trying to, so if that works then something else is going on.

    Have you verified that dagR is of the expected type? According to the documentation, you should be able to just pass the resource descriptor (Rez.Drawables.MyBitmap) directly as the final parameter, but I see that all of the examples use Ui.loadResource() before to get a BitmapResource and then call dc.drawBitmap() on that. Which pattern are you following?

    Travis
  • Have you tried building and running the primates sample program? I draws a bitmap just like you are trying to, so if that works then something else is going on.

    Have you verified that dagR is of the expected type? According to the documentation, you should be able to just pass the resource descriptor (Rez.Drawables.MyBitmap) directly as the final parameter, but I see that all of the examples use Ui.loadResource() before to get a BitmapResource and then call dc.drawBitmap() on that. Which pattern are you following?

    Travis


    Now, I tried that Primates sample and the same result:
    Failed invoking <symbol>
    Invalid Resource
    in onUpdate (/home/sis651/DEV/workspace/Primates/source/PrimatesView.mc:58)
    Connection Finished

    The issue is with the simulator. Eclipse compiles without any errors but only CIQ 1.2.1 simulator can run it, 1.2.4 and 1.2.5 tells this resource issue.

    I declared my drawables in drawables.xml as "<bitmap id="dag" filename="dag.png" />", then load them into memory in onLayout(dc) function as: "dagR = Ui.loadResource(Rez.Drawables.dag);" Then in onUpdate(dc) function draw them using dc.drawBitmap(5, 35, dagR);"

    However, on latest simulators it results in invalid resource error. Also I had an app I build with 1.2.4 which didn't have any bitmaps. Added a bitmap and it doesn't run then.

    If there is no issue in dc.drawBitmap in other users maybe it's an issue with simulator running on Linux. On Linux simulator display for 16 color displays was never good but didn't had resource issues before.
    I'll continue writing on 1.2.1 and publish using 1.2.5... :)
  • I only have the 1.2.4 SDK installed on this machine, but it seems to work fine for me.

    C:\connectiq-sdk-win-1.2.4\samples\Primates>monkeyc -o bin\Primates.prg -m manifest.xml -z resources\bitmaps.xml;resources\resources.xml;resources\strings.xml source\*.mc

    C:\connectiq-sdk-win-1.2.4\samples\Primates>start simulator

    C:\connectiq-sdk-win-1.2.4\samples\Primates>monkeydo bin\Primates.prg
    Found Transport: tcp
    Connecting...
    Connecting to device...
    Device Version 0.1.0
    Device id 1 name "A garmin device"
    Shell Version 0.1.0
    Copying file.... 1% complete
    Copying file.... 2% complete
    Copying file.... 3% complete
    Copying file.... 4% complete
    Copying file.... 5% complete
    Copying file.... 6% complete
    .
    .
    .
    Copying file.... 95% complete
    Copying file.... 96% complete
    Copying file.... 97% complete
    Copying file.... 98% complete
    Copying file.... 100% complete
    File pushed successfully
    Connection Finished
    Closing shell and port
    Found Transport: tcp
    Connecting...
    Connecting to device...
    Device Version 0.1.0
    Device id 1 name "A garmin device"
    Shell Version 0.1.0


    Travis
  • Thanks. Probably it's because of Linux and Wine...
  • Update for my issue with bitmaps on latest SDKs...

    It seems that only drawing bitmaps on 16 color screen devices is problematic. 64 color devices like epix, vivoactive and vivoactive hr works fine.

    Compiler and simulator on Wine on Linux have always been problematic with 16 color devices but at least didn't crashed till SDK 1.2.4... Anyway, uploaded apps on the Store works just as they should.
  • Sounds like it could be an issue with Wine and/or the version of the Java RTE you have loaded with Wine..
  • Sounds like it could be an issue with Wine and/or the version of the Java RTE you have loaded with Wine..


    I think its Wine. Display of 16 color devices have never been good in my soft environment.