I think it would be helpful if you provided some code.
If WatchUi.animate() was not called, then we have no way to know to call onAnimationComplete()... so you must have called WatchUi.animate() at least once.
So it seems that you have animations running…
xoffset = how many pixels to shift the character right (= extra blank pixels to left of character)
yoffset = how many pixels to shift the character down (= extra blank pixels above character)
xadvance = total width of character in pixels (so adds xadvance…
I have a question about reliability of info.elapsedDistance in the simulator (or FIT-file). If I, at the same call to compute in a simple data field,store both info.timerTime and info.elapsedDistance and then later do the same and use those to calculate…
This is definitely a hard one to debug since you can't do it in the simulator. I can't think of any scenario in the simulator where you can "resume" an activity with a new instance. And running it on the Edge requires a several minute…
The best you can do is derive this data from ambientPressure / meanSeaLevelPressure / elevation / altitude / pressurehistory / elevationhistory so it will require a lot of testing (eg with a pressure chamber) to get this right, plus also note if you intend…
I'm not sure what the msg.timestamp is. The documentation says it rolls over every 2 seconds and that it's based on the 32768 kHz
clock
