Under Review
over 1 year ago

Steps Complication changes from Number to Float/1000 when reaching 10K steps

On my Venu2 and on a user Forerunner 955 Solar, once 10K steps are reached, the Steps complication value is no longer a Number but a Float with the steps count divided by 1000, so 15500 steps becomes 15.5 steps. Not sure if it's a feature or a bug, but the documentation is definitively wrong if it's a "feature".

On that subject, in the Simulator, you can't test what happens when 10K steps are reached as the Complication value becomes a number in the billions. My uneducated quess is it also becomes a float but the bytes forming that float are read as a number, hence producing that result.

SylvainGa
Parents
  • 6 months ago

    Ran into this issue as well, but then I noticed the units for the steps complication switch from null to "K" at 10000 steps. I assume the intention is to display > 10000 steps as "10k" in the complication?

    That's interesting bc I thought this change had been made for native watchfaces on some devices, users complained, and it was reverted, which would mean the complications API now preserves the older behavior that ppl don't want. At least that's my hazy recollection from reading forum threads.

Comment
  • 6 months ago

    Ran into this issue as well, but then I noticed the units for the steps complication switch from null to "K" at 10000 steps. I assume the intention is to display > 10000 steps as "10k" in the complication?

    That's interesting bc I thought this change had been made for native watchfaces on some devices, users complained, and it was reverted, which would mean the complications API now preserves the older behavior that ppl don't want. At least that's my hazy recollection from reading forum threads.

Children
No Data