DataFields : 367 RunFields

Many thanks, I dreamed of that sort of datafield (the old habits from looking at the phone screen)!

I have some question and suggestions of improvement (fenix 3, 7 fields):

Q1: I have heard that built-in Garmin instant pace it is in a fact 12s moving average. Is it true? If so, there is no sense replacing it by 10s average. I think that instant pace is crucial for many runners and Garmin will definitely improve it in future.

IMP1: To display the HR with zone color, eg orange. (Change the number color or background color or add colored heart icon - I'm not sure which looks better)
IMP2: To display the CADENCE with "zone" color, according to Garmin table.
IMP3: Two versions of 367. For training and for the official race. For the official race many competitors does not use HRM strap (guess why :) ) and turn the autopause off. So for training Timer would be better than Time elapsed, and for the race Time elapsed id definitelly better than Timer.
For the race (or simply for watches without HRM strap) HR and Caddence could be replaced with other stats, maybe pace 120s moving average or 1km moving average (don't have idea for the second one - you picked already what id need).

Q1 : Short answer - Dunno. In fact, I am thinking of doing 5s moving average instead. (still mulling it over)
IMP1 : HR zones are not exposed by API. hence, can't do anything of that sort unless hard coded (and everyone's zone's different)

IMP2 : now, this is an idea. since Cadence color are, as you said - according to garmin's table - this is nice. But problem tho, the Colour. Currently all the fields are NOT segregrated. I guess I can box it up into 7 diff boxes much like the 4 field layouts kind of thing. not sure how good that would look tho. But, interesting nevertheless. Will put it as KIV

IMP3 : Right now, I'm using elapsed time cos I turn autopause off anyways. I use the HR strap everytime. if not mistaken - the timer is not exposed by the API and thus, one has to manually keep track of all the pauses or time when the speed (pace is not exposed by the API - pace is derived from the speed) goes down to say < 1kmh.

hmm.. i stand correctted - it IS exposed (http://developer.garmin.com/downloads/connect-iq/monkey-c/doc/Toybox/Activity/Info.html), so that wouldn't be too bad.

Honestly, right now, my itch is scratched - I'll KIV on the items above - the Timer and Cadence is promising and at a glance, don't seem like will take too much time given my skill level.

Thanks for the feedback!! And you know where the donation link is :-p

I just tried it.. looks "awful" in some ways :-p

if ( Cad.toNumber() > 185 ) {
dc.clear();
dc.setColor(Gfx.COLOR_PURPLE, Gfx.COLOR_TRANSPARENT);
} else if (Cad.toNumber() > 174 && Cad.toNumber() < 185) {
dc.clear();
dc.setColor(Gfx.COLOR_BLUE, Gfx.COLOR_TRANSPARENT);
} else if (Cad.toNumber() > 163 && Cad.toNumber() < 173) {
dc.clear();
dc.setColor(Gfx.COLOR_GREEN, Gfx.COLOR_TRANSPARENT);
} else if (Cad.toNumber() > 151 && Cad.toNumber() < 162) {
dc.clear();
dc.setColor(Gfx.COLOR_ORANGE, Gfx.COLOR_TRANSPARENT);
} else {
dc.clear();
dc.setColor(Gfx.COLOR_RED, Gfx.COLOR_TRANSPARENT);
}


Also since the location of the datafields are based on "fit", they are not exactly centered and thus, putting boxes would make them not pretty :-p
i'll see how.

Thank you for quick feedback.

I understand now the limitations of API. Thought that Garmin gives us every stat. You're right that heart rate zone hardcoding is pointless.

So, you are saing, it is a challenge to have good looking colored field? I can imagine that. :)

Thanks for the work.
It is a pity that on the Vivoactive only 2 lines work.
Anyway, when the 3 lines work, I have a suggestion for you as to the Vivoactive 9 fields:
DIST ELAPSED TOD
SPEED CAD HR
A SPD A CAD A HR

I meant for the 367 BikeFields

Those bottom are actually already in the code.
There's a bug in the way the VA displays the resolution and how I'm choosing to do decide which fields to show.
If u read a few pages back - it's been talked about and a ticket opened for it)

Glad u like it. Do donate.

There's a bug in the way the VA displays the resolution and how I'm choosing to do decide which fields to show.

FYI, The device context for the bottom field is getting updated for VivoActive. I believe it has been integrated and will be in the next device firmware release.

Great datafield. Thanks a lot.
Any chance you could change elapsed field with timer?

Regards!

Glad you like it!! Regarding the timer, It's been discussed.

Have you considered donating to the effort? :-p

FYI, The device context for the bottom field is getting updated for VivoActive. I believe it has been integrated and will be in the next device firmware release.

Thats good to know!! Thanks Brian.