InfiniTime

InfiniTime copied to clipboard

The source for this data is https://www.uwyo.edu/wintherockies_edur/win%20steps/coordinator%20info/step%20conversions.pdf .

For now this is just an integer as it is the only way I can figure out how to format the string into the label. In the future, a more precise distance would be ideal in the future (up to hundredths).

---

I resized some things like the "reset" button so the item would fit. At first I thought to create a new screen (like Settings does, swipe down to next screen) but for one bit of data, unless a more advanced UI is made this is the easiest way.

Perhaps it could switch between showing steps and showing kilometers by tapping on the screen, as it's basically the same information.

perhaps this number should be configurable. adding UI to do that, I think it overkill - but maybe just a number inside a file, and then it can be changed over the FS. (and read it only once per boot or something like that)

I'm on vacation, I just did this shortly because it was raining. I'll review everything eventually

perhaps this number should be configurable. adding UI to do that, I think it overkill - but maybe just a number inside a file, and then it can be changed over the FS. (and read it only once per boot or something like that)

I do not know how far we are in terms of BLE/FS. If I knew we were I would probably add a pdf/ebook reader lol.

But this number should be configurable via a setting. And overall I guess the Steps file could use a good cleanup.

perhaps this number should be configurable. adding UI to do that, I think it overkill - but maybe just a number inside a file, and then it can be changed over the FS. (and read it only once per boot or something like that)

I would love to have this on the watch itself, because even though Gadgetbridge already does this (it lets you configure your pace length and displays distance walked among other things), I don't want to have to pair my watch to my phone at all. I think a dedicated panel in the settings app would be the best option as I don't have to mess with anything over Bluetooth.

For the initial implementation, a static value is fine. Let's not expand the scope of this PR too much.

Makes sense...

We've decided to close the issue #883 and not add this feature.