4.0 - Upcoming wearables

I'm exited about the new wearables that are coming up!

However, can we rely on the specs that are given in the simulator.json files in the devices of the SDK? I mean, screen sizes, elevation support, fonts,...? Can we actually start adapting our clocks/apps to these new devices? Or is it safer to wait?

Top Replies

jim_m_58 over 5 years ago in reply to flowstate +1

This has been done in the past - Anyone remember "Tall Watch", "Round Watch", etc?

It's so when the "upcoming devices" are announced, there are a bunch of apps available in…

All Replies

9635560 over 5 years ago in reply to Brandon.ConnectIQ

Ok, let me know when docs are available.

On a related note, has "requiresBurnInProtection" gone somewhere weird? Or, indeed, onEnterSleep / onExitSleep?

9635560 over 5 years ago in reply to 9635560

Ah! Ignore me - that's a coding issue.

jim_m_58 over 5 years ago in reply to 9635560

It's in the API doc for preview 3. Just not a note that it should be used on 4.x devices. I first saw it in the preview 1 API doc.

SDKroot/doc/index.html

In eclipse, the Connect IQ menu, Api doc

or in VS Code, Monkey C: View documentation in the command palette

The web doc probably won't be updated until 4.0 becomes the production SDK.

9635560 over 5 years ago in reply to jim_m_58

Thanks Jim, I can find how to get the BufferedBitmapReference now, but I can't for the life of me see how to get a dc to actually use it!

Travis.ConnectIQ over 5 years ago in reply to 9635560

If you have a Reference class, you need to call get() to get access to the underlying resource object. Once you have that, you should be okay.

This will be in the API docs that are included with the SDK build, but you'll be digging around. We don't just spell it out for you.

9635560 over 5 years ago in reply to Travis.ConnectIQ

Cool, I'll give it a go - thanks.

I'm sure it'll all make sense pretty quickly like the rest of ConnectIQ.