Data Field: Race Field

Feedback and a little bug

Hello TORSTEINVH!

This is a pretty useful and nicely designed datafield! Thank you for sharing this!

On my Edge 820 I see a little bug with the displayed time in the lower right corner, see attached screenshot. Basically the last digit is not visible. It would be really great to get this fixed as I could then use a diferent data field in the top middle.

Furthermore I have a suggestion: It would be useful to be able to set the metric used in the "bargraph" which currently shows the cadence. Personally I would rather use power here instead. Of course this might need some thinking, like how many zones to display for a given metric (7 for power, 5 for HR for example...) and which metrics make sense (HR,power,cadence,speed?), maybe let user define min/max or all the zones' border values.

One solution could be to add one drop-down field in the user settings to select which metric to use here and for example 10 user data numeric input fields to define max 10 zones and user has to enter the begininng value for each of these zones (either as percentage of another defineable value or an absolute value).

If user enters "-1" (or 0), then this field is skipped and reduces the number of visible zones so that anything from 0-10 zones would be possible. Coloring of the zones should probably be derived from HR/power zones and maybe a given zone of said 10 max zones has a given color so that if the user wanted, he could skip any given zone by entering said -1 and as a result user would be able to influence (to a certain extend) which (later visible) zone has which color...

Just a quick update.
I'm working on a small update fixing some bugs, and plan on a more major revision later in the summer.

Fenix 5?

I'd love to try it on my Fenix 5

Fenix 5 version is also planned :)

Just a quick update.
I'm working on a small update fixing some bugs, and plan on a more major revision later in the summer.

Is the imperial distances in the splits something you're working on? In the meantime, can I just up the distances on the phone so they come out right on the 820? Meaning, if I want 56 miles, I put 90 in the settings and it comes out 55.9 on the 820 - will that calculate the split times right?

I know about the imperial bug, and it is on my list of things to fix.
The workaround you describe should work, but please test it on a short distance before relying on it.

I'll be testing it this weekend on a 56-mile course. I won't be relying on it but will keep an eye on it.

One note along those lines - it seems I can't get an exact mileage. If I put in 90 miles for it to "convert" it, it converts it to 55.9. If I put in 90.5, it still converts to 55.9. Just a heads up on that.

I really like the app. If I could throw in a few feature requests, it would be to somehow have more splits, an easier way to set them up on the phone, and some more field options.

Thanks again for all the hard work!

I'll see what I can do about features, currently the app has only 1K free memory left, so I may have to take something out in order tp put something new in.

The split setup is complicated for the end-user, but efficient memory wise, but I'll see what I can do.

As for field options, what are you missing?

-Torstein