Acknowledged

FIT Write Bug

This is a bug related to rendering the FIT Write Data. A difference between Garmin Connect Mobile and Garmin Connect Web.

I can't post an image here so I'll include it in the reply.

In Garmin Connect Web, as I move the mouse to the right, values stop at 2 hr, 11 mins. That was when the CIQ data field experienced a crash. My Garmin 1030 rebooted near the end of the ride, restarting the FIT Writes. So the descending line to ZERO is correct.

However, in Garmin Connect Mobile, the line continues straight across that gap. Looks like a simple rendering bug. Not sure which you prefer, but they should be the same.

Parents
  • > In general, for any given data type, the invalid value is the largest representable positive number.

    For any given *integer* data type, I should've said.

    For floating point values it's all bits set to 1 and for strings it's 0.

Comment
  • > In general, for any given data type, the invalid value is the largest representable positive number.

    For any given *integer* data type, I should've said.

    For floating point values it's all bits set to 1 and for strings it's 0.

Children
No Data