With the 20 second transfer time you give and the provided resolution, it is transferring around 2880 pixels per second, with the bits per pixel unknown. If it is 8 bpp, then 2.8 kBps isn't too bad imo, not…
What about making getting a label's text at runtime, is it possible to "bind" it to some variable?
There is no such thing as instantaneous pace when given discrete position inputs as provided by GPS. Pace is calculated as the change in position over time, so you need at least two position and time points
Nice!
No worries, this exact situation has happened to others in the past, so I'd say that it's more of a UI/UX issue on Garmin's part. (Especially since in some contexts, people use "workout" synonymously with "activity".)…
Unfortunately there are/were a couple of quirks in current watches like Forerunner 955 / 965 (and probably at least every other 5-button touchscreen watch of their generation):
Bug 1) A right swipe from the left edge triggers onKey(KEY_ESC) and not onSwipe…