System 7 questions

Couple of Questions for Garmin, related to System 7:

1) Have you considered skipping API 5 and 6, and go straight to 7, to make System and API level line up??? There is plenty of confusion with the whole API vs system level as is.

2) Have you considered making a way to select the compile version in the manifest or something?? System 7 seems to bring some (needed/nice) changes to core stuff, so there is no backwards compatibility with old System 4/5/6, right??? If one just needs to quickly fix a bug in an old app, might not make sense to update the code. Would be nice if the level was selected in the project, rather than only in the SDK manager.

3) Is there a list of which devices will get System 7 support? Surely VENU 3 and VA5 is on the list right?

Top Replies

All Replies

jim_m_58 5 months ago in reply to Fsallstrom

As a work around (may be not exact), keep track of how many times compute is called and do the request once every 60 times, as compute is called every second.

Fsallstrom 5 months ago in reply to jim_m_58

of course! quite brilliant, why didnt I think of that :-)

jim_m_58 5 months ago in reply to Fsallstrom

You can also use elapsedTime

Fsallstrom 5 months ago in reply to jim_m_58

Assuming elapsedTime is the elapsed time for the activity, it can't get zeroed when I make the web request so if I use that approach, I need to MOD elapsedTime by 60000 ms, which is the same approach as just incrementing a NUMBER var in the compute function and MOD it by 60. Or do I misunderstand?

jim_m_58 5 months ago in reply to Fsallstrom

They both should work so it's whatever you prefer.

Fsallstrom 5 months ago in reply to jim_m_58

alright, thanks

sabeard 5 months ago in reply to Fsallstrom

Data fields have a built in timer. The compute function is called every second. You can set a countdown variable, for the number of seconds between web requests. Each cycle through decrease by 1. When you get to zero send the next request and reset the countdown. Instant timer.

FlowState 5 months ago in reply to Fsallstrom

Fsallstrom said:
I need to MOD elapsedTime by 60000 ms, which is the same approach as just incrementing a NUMBER var in the compute function and MOD it by 60

Those two things aren't the same approach.

If you calculate elapsedTime mod 60000 every time compute is called, and only fire off a web request when the result is 0, that's not the same approach as incrementing (or decrementing) your own timer variable.

The reason is that compute isn't called *exactly* every second, and elapsedTime likely won't be an even multiple of 1000 on each call to compute(), which means your web request won't fire every minute, and there's a good chance that it will never fire.

flocsy 5 months ago in reply to FlowState

that's true, but it can be improved. For example you can save the last value of elapsedTime % 60000 (every time compute is called) and fire when the current elaprsedTime % 60000 is less than the saved value.