jim_m_58 said:

There is really no 1 field layout. You can have 2 fields or more.  The subscreen is a field, and the screen except the subscreen is a field

I see, that explains the following output with my test code, when I select 2 fields in the sim for…

Can't speak for who you're replying to, but depending on the context, "hard reset" can either mean (forcibly) turning the device off and on, or factory reset / reset to default state.

If I had to guess, I'd say they were referring to…

I meant that maybe the native elevation field is displaying something other than what is written to the fit and that can also be different from what is being returned in the SDK. At least that's how it looks like from the graph.

As for testing: logging…

Not saying this isn't a bug, but I think the expected workflow is:

- you make a change to barrel source

- you compile the project which uses the barrel (as opposed to compiling the barrel itself)

I realize this breaks down if you have more than one…

Actually I was wrong. _screenCenterPoint shouldn't change.

But at the very least, you need to change the definition of generateHandCoordinates to

private function generateHandCoordinates(centerPoint as Array<Number>, angle as Float, handLength as…

That's a graphical DF, it has nothing to do with SimpleDataField. What I and seemingly other developers want is to be able to use SimpleDataField (because it does give lot of features "for free") that we want to use and that is almost enough for our needs…

This information is 8 months old, but someone else found that no level beyond -O2 seemed to do anything more than -O2 at the time. For what it’s worth, I think all of the options have been available since optimization was first added to the compiler,…

No, there aren't enough buttons to support button actions for data fields. Every single button already has a use during an activity.

There is one hacky "interaction" I've used - a quick onHide() / onShow(). From the user's POV, they need at least…