Acknowledged
5 months ago

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.

DaveBrillhart
Parents
  • over 2 years ago

    Since Monkey C obviously doesn't have integer types smaller than 32 bits, I would just use the smallest Monkey C integer type possible (Number for 8 to 32 bits and Long for 64 bits), and make sure your value doesn't overflow.

Comment
  • over 2 years ago

    Since Monkey C obviously doesn't have integer types smaller than 32 bits, I would just use the smallest Monkey C integer type possible (Number for 8 to 32 bits and Long for 64 bits), and make sure your value doesn't overflow.

Children