Connect IQ 1.2.0 SDK beta!

This morning we released a public beta of the 1.2.0 Connect IQ SDK! The beta SDK will allow developers to get their hands on the fun stuff we've been putting together lately, and gives everyone a chance to update their apps to take advantage of these new features. In addition to the SDK beta, there are also beta firmware releases for all current Connect IQ devices to include support for the 1.2.0 SDK. You can read about the details, as well as find links to the SDK and firmware downloads, over on our developer blog:

http://developer.garmin.com/index.php/blog/post/announcing-connect-iq-1.2

Just a couple of notes:

We've temporarily disabled the ability to build app packages via the App Export Wizard (which creates .iq files) to avoid 1.2.0 beta apps from making their way to the Connect IQ app store until we are out of beta. Developers will be able to create PRG files with the Build for Device Wizard, however, which can be side loaded for testing on devices. If you're planning any updates to apps that are on the store, and the updates don't require 1.2.0 SDK features, build with the 1.1.4 SDK so you'll be able to publish those updates to the app store.
If you plan on trying out the 1.2.0 SDK beta, please be sure update your Eclipse plug-in to version 1.2.0 by clicking the Help > Check for Updates menu item.

Kyle.ConnectIQ over 9 years ago

Sdk 1.2.0

Could you tell us the permissions in your SDK/bin folder?

1. Open Terminal

2. cd <sdk folder>/bin 

3. ls -al

4. copy the output of that command here or email to [email protected]

Also, as mentioned by myronuecker, did you try downloading from the website instead and setting that as your SDK? If you have, did this fix the issue for you?

ruperthawkes over 9 years ago

Bug !

Setting both the alarm count and notification count to 1 in the simulator then rebuilding the app seems put

4294967295

in the alarm or notification count value!

ruperthawkes over 9 years ago

Can we PLEASE have a WORKING example of how to use a list in the settings config?

The docs are just not clear. How can I set up the config files to actually have a list in the settings!?!?!?!

jim_m_58 over 9 years ago

Can we PLEASE have a WORKING example of how to use a list in the settings config?

The docs are just not clear. How can I set up the config files to actually have a list in the settings!?!?!?!

Have you looked at this thread? https://forums.garmin.com/showthread.php?325843-User-application-settings

Former Member over 9 years ago

I tried the solution mentioned by myronuecker, this has worked for me. I have deinstalled the sdk version that was installed via Eclipse and installed it manually. After that it worked perfectly.

To get the permissions for you i have to install it again. If you would like that, please let me know.

Could you tell us the permissions in your SDK/bin folder?
1. Open Terminal 2. cd <sdk folder>/bin 3. ls -al 4. copy the output of that command here or email to [email protected]

Also, as mentioned by myronuecker, did you try downloading from the website instead and setting that as your SDK? If you have, did this fix the issue for you?

Stanislav.Bures over 9 years ago

dokumentation mistake

- (Object) drawArc(x, y, r, attr, degreeStart, degreeEnd)

Use drawArc() to draw an arc. 0 degree: 3 o'clock position. 90 degrees: 12 o'clock position. 180 degrees: 9 o'clock position. 270 degrees: 6 o'clock position.

Parameters:
x (Number) — X location of arc center
y (Number) — Y location of arc center
r (Number) — radius of arc.
attr (Number) — Arc drawing attributes. (ARC_COUNTER_CLOCKWISE or ARC_CLOCKWISE)
degreeStart (Number) — The start angle of the arc by degrees.
degreeEnd (Number) — The end angle of the arc by degrees.
Since:
1.0.0

drawArc is working perfectly but only with SDK 1.2

PiotrekZ5 over 9 years ago

My Simulator ( SDK 1.2.0) shows that the memory limits for Epix are as follows:

DataField: 128 KB
Widgets: 1024 kB
Watch Face: 1024 KB
Watch App : 1024 KB

Is it true?

Brandon.ConnectIQ over 9 years ago

Yes, that's correct. The epix has a lot more memory available than the other current wearable devices, so we were able to loosen our memory limits quite a bit on the epix. :)

PiotrekZ5 over 9 years ago

This is very good news :).

By the way. It will be nice to have possibility to make some settings in application directly in watch. I thought, that this could be solved in that way:

- suppose that we have application MyApp
- we can write second application MyAppSettings.

<application_name>Settings works on the same data storage as <application_name>.

It shouldn't be difficult to do and gives unlimited possibilities without wasting memory during course of main application (<application_name>).

MoxyRoger over 9 years ago

This would be especially useful if a watch App could change settings for a watch Face or a DataField because they don't have user input capability on their own.

The MyAppSettings and MyApp combination would be useful even if both were Apps because it could be used to free up memory in MyApp.