Version 0.4
fenix 3
https://apps.garmin.com/de-DE/apps/843ae566-db0d-40ae-bbf7-c16bea5f944d
This data field view has been developed because of the thin number fonts in multiple data field views on fenix 3. Multiple data field views are very difficult to read especially for people who normally need reading glasses.
Because of the limitations of Connect IQ SDK this data field view has following drawbacks:
- it has 4 fixed data fields that I feel most important for long distance running (configuration is not possible)
- a lap is always 1 kilometer (or also 1 mile in next version), LAP key is not recognized
The 4 data fields are:
- Timer up to 99 hours
- Heart Rate
- LAP Timer up to 99 minutes
- Total Distance up to 999 km
Some of these data fields are dynamic in their presentation dependent on current value:
Timer (upercase letter means large bold font, lowercase letter means small bold font)
- 00:00:00 ... 00:59:59 shown as MM:SS
- 01:00:00 ... 09:59:59 shown as H:MM:SS
- 10:00:00 ... 99:59:59 shown as HH:MM ss
Total Distance
- 0.000 ... 0.999 km shown as meters
- 1.000 ... 19.999 km shown as kilometers with 3 digits precision
- 20.000 ... 199.999 km shown as kilometers with 2 digits precision
- 200.000 ... shown as kilometers with 1 digit precision
Inspite of the limitations of Connect IQ SDK, I would like to improve the data field view. From feedback messages I got following requirements:
- instead of Lap Time, try with current pace i.e min/km
- LAP PACE or AVR.PACE instead of LAP TIME
IMPORTANT: Before I develop next version of this data field view, I would like to get some feedback:
What do you think about these requirements?
What is more important, current pace, lap pace or average pace?
What other data fields are more important than that the view already has?
Regards
Gunar