elapsedDistance

Thank you for looking into this. I saw several confirm that strange behavior back when I reported it. But I just tested my current VSC IDE and elapsedDistance is incrementing now. I can't reproduce it. So I assume an SDK update might have fixed it. Or possibly the new VSC plugin? Anyway, we are good now it seems. 

Hello DaveBrillhart ,

I was unable to reproduce this issue in the simulator setting the SDK to 7.4.3, I did have to lower the supported API level to get support for the 1030 since we don't support it with newer systems, are you seeing this issue with other devices on newer systems? 

If you have any more information on how you were reproducing this issue, I would be happy to continue to look into it. Here is how I attempted to reproduce the issue.

1. Set the Minimum Supported API Level to 3.2.0 - System 4, and changed the SDK version to 7.4.3
2. Ran a test app that uses elapsedDistance on Edge 1030
3. Go to Simulation -> Activity Data, select START and then Play
4. Saw that elapsedDistance was increasing, the same was happening when hitting Play and then Start

If you have any more information or something else to check let me know otherwise we are going to close this for now.
Here are my results:

I agree that the UI for Simulation > Activity Data is a little confusing (and was even worse in the past), but I think the buttons in the data field timer controls are supposed to do exactly as described: Start, (Auto) Pause / Resume, Stop, Save, Discard, (take) Lap, (end) Workout Step, (advance to) Next Multisport (leg). More to the point, most of them correspond with various CIQ data field event handler functions. So if there's any confusion or inconsistency with the buttons in the sim, the same would have to be said of the corresponding event handler functions, I think.

My understanding of these various buttons:

- Start (onTimerStart): equivalent to pressing to the Start button when the activity is stopped

- Stop (onTimerStop): equivalent to pressing the Start button when the activity is running

- Pause / Resume (onTimerPause / onTimerResume): equivalent to the auto-pause (and resume from auto-pause) device actions

- Save: equivalent to selecting Save in the menu when the activity is stopped (possibly causes onTimerReset to be called)

- Discard: equivalent to selecting Save in the menu when the activity is stopped (possibly causes onTimerReset to be called)

- Lap (onTimerLap): equivalent to manual or auto lap

- Workout Step (onWorkoutStepComplete): equivalent to advancing to the next workout step (by pressing the lap button during a workout)

- Next Multisport (onNextMultisportLeg): equivalent to advancing to the next multisport leg (e.g. by pressing the lap button during a multisport activity)

I think all of these should be fairly straightforward other than possibly pause / resume (if you don't use the auto-pause functionality irl), and save/discard (because it's not clear whether onTimerReset will be called or not).

It's obviously also possible to click on the actual device buttons in the simulator for most of this functionality. It's just too bad that either for practical reasons, or because the simulator doesn't simulate the full device UI, not all of these functions can be triggered "naturally". e.g. If you stop the activity, you're not going to see the menu that's normally displayed

- The Play/Pause button is for starting/stopping FIT file playback or simulation

I think the biggest problem with this UI is that it's possible to click Save Fit Data before you've clicked Save in the timer controls. When you do this, the simulator will dutifully save a corrupt FIT file that can't be opened by monkeygraph (for example). The same problem has existed since the beginning, and there were definitely posts in the forums from people wondering why they couldn't use the FIT file that was saved by the sim.

Idk, in general it fits with Garmin's rep for not being the strongest at UI/UX. One could argue that it's confusing for the FIT playback control and the timer controls to even be on the same on the same dialog. (Then again, I can understand why they are on the same dialog.)

I was never been able to understand how those buttons are supposed to work, and whether they work strangely (compared to my expectations) is because they mimic the real devices or because they just work well... randomly.

BTW it's unclear from your report whether this has changed in recent simulator versions, or it was always the same.