SDK 1.2.5 available

Just downloaded it, odd it's not been announced here.

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.
  • This seems to be a Good Release (memory standpoint)

    Prelims 5min tests

    1st Startup Subsequent Starts
    1.2.1 34672 34816
    1.2.5 34552 34696

    so, there is approx 120bytes more memory.
  • Former Member
    Former Member over 9 years ago
    For now, just turn it off as a target when you want to package. No one will have it for a while yet.


    Yes, that's of course what I did, but I'd expect that when the SDK supporting the new device is released, the app submission system should be also updated for the new devices specs. Otherwise, what's the point of releasing an SDK that can build a package the app submission system would not accept?
  • Otherwise, what's the point of releasing an SDK that can build a package the app submission system would not accept?


    The point is to allow developers to port their apps to the new device layout as early as possible. That way when the app store supports the device, the software is ready.

    That makes a lot more sense than rolling out the website, then the SDK, and then waiting for developers to port their applications over to the new devices.
  • Otherwise, what's the point of releasing an SDK that can build a package the app submission system would not accept?


    As Travis said it's so that people can develop/convert stuff for it and be close to ready or ready in time for people getting the device. It seems the actual devices won't be shipping for a month or so, and in that time they may make changes with something in the FW that may mean a new SDK before apps are "store ready".