SDK 1.1.1 Release Available!

We recently released version 1.1.1 of the Connect IQ SDK yesterday, and it's available for download:

http://developer.garmin.com/connect-iq/sdk/

You may also download through the Connect IQ SDK Manager in Eclipse, by clicking the Help menu, selecting Open SDK Manager, and then clicking the Download button for Connect IQ SDK 1.1.1 released April 20, 2015.

v1.1.1

Do not support swipe up/down in simulator to match current device behavior
Fix simulator onHold() event reporting incorrect coordinates
Fix corrupted 1-bit palette bitmap display
Fix size/alignment of round watch display region to prevent clipping
Add Japanese Gregorian translation
Add English support to APAC devices
Add Thai language support
Disable "Not Set" language option for running applications
Allow applications to pass an input delegate into Ui.pushView() when creating a progress bar. The progress bar should only be able to be popped if the developer specifies an input delegate when pushing the dialogue. If null is passed then the progress bar will remain on-screen regardless of input.
The simulator now kills an application when pressing back on the base page
When adding a Duration to a Moment, Duration.value() will now return a long to avoid floating point number precision loss
Fix several stability issues with the geometry iterator
info.StartLocation now correctly initializes to null on devices
getSystemStats() now returns the correct used/free/total memory amounts
The FIT recording session will now be saved when a new session is created, or if the application is closed
The dst field in Toybox::System::ClockTime is now correctly populated
Activity monitoring history now uses the UNIX time epoch
Calling Toybox:System::println(null) now correctly prints "null"
Fix issue where Toybox::Application::deleteProperty() would not always delete a specified property depending on call order with setProperty()
Changing the content of a property ID from a string to a number using Toybox::Application::setProperty() will no longer result in a crash
Using a sub sport greater than SUB_SPORT_FLEXIBILITY_TRAINING should no longer give an unexpected type error
Fix several device crashes and memory leaks under various circumstances
Various other minor bug fixes and documentation updates

Known Issues:

Exceptions are not working correctly

-The Connect IQ Team

Kyle.ConnectIQ over 10 years ago

Any 10 makeJsonRequests. Even if you just run the same thing 10 times. It's an issue I first reported a month or so ago. As long as you make the call, crash after 10! Kyle acked the error and said it would be fixed, and I'd hoped this would be the fix!

It got fixed right after the release. It was delayed due to issues in the Mac simulator due to the change. Sorry to get your hopes up that it'd be fixed in the upcoming release.

pprimoz over 10 years ago

SDK 1.1.1 (4wins) is available for downloading here http://developer.garmin.com/downloads/connect-iq/sdks/connectiq-sdk-win-1.1.1.zip

other downloads http://developer.garmin.com/downloads/connect-iq/sdks/

Former Member over 10 years ago

Nice list! You guys should educate the watch FW guys what a release note section should look like...

Seechunyan over 9 years ago

Am I right to say that the makeImageRequest function is still not ready?

Also is onEnterSleep and onExitSleep available for 920xt yet? Can we somehow simulate it on the simulator too?

Thanks.

travis.vitek over 9 years ago

I don't know about makeImageRequest() but the sleep stuff has been there for quite a while. You need your view class to inherit from Ui.WatchFace. Once you do that, the options for simulating low power mode are enabled in the simulator.

Travis

Seechunyan over 9 years ago

Thks Travis for ur advice.

Actually what happen is that my analog watchface display is stuck until the user presses a button. I saw on the forum somewhere that these two methods may not be available on 920xt yet.

I have already implemented and tested on the actual watch but there is no response and the time display still does not get updated.
I also do not see that option in the simulator. Is it because it's a watchface?

function onEnterSleep() {
Attention.backlight(false);
Attention.playTone(TONE_FAILURE);
}

function onExitSleep() {
Attention.backlight(true);
Attention.playTone(TONE_SUCCESS);
Ui.requestUpdate();
}

Kyle.ConnectIQ over 9 years ago

Am I right to say that the makeImageRequest function is still not ready?

Unfortunately makeImageRequest() is not ready. This will be coming in a future release.

Actually what happen is that my analog watchface display is stuck until the user presses a button. I saw on the forum somewhere that these two methods may not be available on 920xt yet.

The 920 supports these functions now. Off the top of my head I'm not sure what version this support was added but it's been a few months.

As Travis suggested, does your class inherit from Ui.WatchFace? If it doesn't, the Enter/Exit sleep options will not be available in the simulator and it'll not work on the device.

Seechunyan over 9 years ago

Unfortunately makeImageRequest() is not ready. This will be coming in a future release.

The 920 supports these functions now. Off the top of my head I'm not sure what version this support was added but it's been a few months.

As Travis suggested, does your class inherit from Ui.WatchFace? If it doesn't, the Enter/Exit sleep options will not be available in the simulator and it'll not work on the device.

Thanks for the advice. I already use sdk v1.1.1 and implemented the ui.watchface.

Former Member over 9 years ago

function onEnterSleep() { Attention.backlight(false); Attention.playTone(TONE_FAILURE); } function onExitSleep() { Attention.backlight(true); Attention.playTone(TONE_SUCCESS); Ui.requestUpdate(); }

You will not be able to use the Attention module from a watchface. It's possible you aren't seeing anything happen because the methods you're trying to call aren't available. However, I would expect an error to occur (not nothing happens) in that case. Might I suggest using Toybox.System.println() to see if the methods are being called.

Seechunyan over 9 years ago

You will not be able to use the Attention module from a watchface. It's possible you aren't seeing anything happen because the methods you're trying to call aren't available. However, I would expect an error to occur (not nothing happens) in that case. Might I suggest using Toybox.System.println() to see if the methods are being called.

Thanks for the suggestion but before this code snippet, these two methods only have system.println and i cant find it on simulator. Thus i changed it to try and test on watch. But still nothing thus i tried attention. But guess attention is not available to watchface.

Will try and debug on 920xt again if someone has already solved this problem. But so far other analog watchface i tried have same issue.