I'll first say, this was a bug in my code and I fixed it, but it did uncover a bit of weirdness that one of my beta testers said even crashed a va (fw 3.00).
The app records a run or a walk. I allow for pause/un-pause (recording.stop/recording.start)
if while the recording is "paused" (recording.stop), addLap() is called, the FW does get in a mess, and you see things like std "save/discard" screen, and if you do a save, the va requires a hard reset.
In my code I now don't call "addLap()" if paused, but this is probably something that should be added to the list...
"calling addLap() when the recording is stopped does really weird stuff"
