Am I misunderstanding documentation or is this a simulator bug? getSubscreen

Hi,

Was trying to find the location of the little wheel for semioctagon screens and thought that an ideal candidate for doing this would be:

https://developer.garmin.com/connect-iq/api-docs/Toybox/WatchUi.html#getSubscreen-instance_function

But when I try to test (yes, testing for a semioctagon device), it won't compile.

EG: I include the line:

System.println("DRAW FEATURE "+WatchUi.getSubscreen());

And I see the console output:

ERROR: instinct2: E:\gdcsoft\SVN_GARMIN\WatchFace_RomanNumerals\source\WFView.mc:218: Undefined symbol "getSubscreen" detected.

AFAIK, I am on the most current SDK - 4.0.9 - so this looks a lot like a bug... or do I need to do something else?

Bemused of Dublin

Top Replies

jim_m_58 over 3 years ago in reply to 9635560 +1 verified

Scroll down. 4.0.10 shows after 4.0.2 and before 4.0.1. There's a issue with the sort order in the SDKmanager that will be fixed in the next SDKmanger release.

All Replies

0 jim_m_58 over 3 years ago

You need to use the 4.0.10 SDK. See https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/garmin-introduces-the-instinct-2-series

"The Instinct 2 requires Connect IQ SDK 4.0.10. Get the latest SDK and the Instinct® 2 device configuration with the SDK Manager. Learn more about the Instinct® 2022 personality in the User Experience Guidelines."

4.0.10 is the most recent SDK, but the order in the sdk manager is odd in that it shows 4.0.10 between 4.01 and 4.0.2 (Kyle said this will be correct when the 4.1.1 SDK is released)

In addition to getSubscreen, it also has the semioctigon screen shape:

SCREEN_SHAPE_SEMI_OCTAGON

API Level 3.3.0

I have a number of apps ported to the Instinct2/2s, and with the 4.0.10 SDK, getSubscrren() works fine.

bb=(WatchUi has :getSubscreen) ? WatchUi.getSubscreen() : null;

"bb" is the bounding box on the Instinct2 devices, or null on other devices.

Also in https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/the-real-devices-of-connect-iq-part-1

note this:

"With the Instinct 2S, the sub-screen extends a few pixels past the primary border of the screen. To allow drawing to the full sub-screen area, the Dc.getWidth() extends to include the sub-screen. This means that while the screen advertises itself as 163x156, outside of the sub-window it is 156 x 156. The seven pixels to the right are under the lens. Data fields will advertise their boundaries correctly."

0 9635560 over 3 years ago in reply to jim_m_58

Ah, ok, thanks.

I thought 4.1 was just a beta though? It's certainly listed as just a beta in the SDK manager, are we supposed to be using that for release compile?

0 jim_m_58 over 3 years ago in reply to 9635560

Not 4.1.0, 4.0.10. getSubscreen works with 4.0.10, it's not a beta SDK, and you can publish apps for the Instinct2/2s in the store.

Here's the apps available for the Instinct 2 in the app store.

apps.garmin.com/.../apps

0 9635560 over 3 years ago in reply to jim_m_58

Hmm.

AFAIK, I have the latest SDK Manager - I just redownloaded and did a compare directories and both were identical.

I do not have access to the latest SDK.

This is what I see:

+1 jim_m_58 over 3 years ago in reply to 9635560

Scroll down. 4.0.10 shows after 4.0.2 and before 4.0.1. There's a issue with the sort order in the SDKmanager that will be fixed in the next SDKmanger release.

0 9635560 over 3 years ago in reply to jim_m_58

GAH!

Software sucks.

Ok, thanks Jim, got it now.

0 jim_m_58 over 3 years ago in reply to 9635560

Here's a post from Kyle about the fix:
https://forums.garmin.com/developer/connect-iq/f/discussion/285506/the-instinct2-s-require-vs-code-to-run-the-sim/1375728#1375728