Name: Bold Data Field Metric
Rating: 4.2 (12 reviews)
Author: georg.il

Specialized 4 DATA FIELDS VIEW designed for long distance running using a LARGE BOLD FONT.

DESCRIPTION
===========

I have designed this data field view because original number fonts for multiple data field views are quite small and therfore very difficult to read for people that normally need reading glasses. I had a 310XT before which was much better readable than the new fenix3.

The view is very specialized because 
- it has 4 fix data fields that I feel most important for long distance running
- a lap is always 1 kilometer because of the limitations of Connect IQ API
- unit is always meter/kilometer

The 4 data fields are:

- Timer up to 99 hours
- Heart Rate
- LAP Timer up to 99 minutes
- Total Distance up to 999 kms

Some data fields are dynamic in their presentation and precision dependent on current value (see the different screen shots):

Timer  (upercase letter means large bold font, lowercase letter = small bold font)
-   0:00:00 ...   0:59:59       shown as MM:SS
-   1:00:00 ...   9:59:59       shown as H:MM:SS
- 10:00:00 ... 99:59:59       shown as HH:MM ss (seconds in small font)

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

KNOWN ISSUES
=============

1. Becaus of the lack of API function for accessing LAP timer, it is quite difficult to determine when a LAP is over and a new one begins. Therefore a LAP is always defined as 1 kilometer and the LAP key is not recognized. 

2. My algorithm fo recognizing LAPs bases on status of kilometer value changes. Unfortunatly, everytime a LAP is reached, the AUTO LAP function shows the LAP results display for some seconds. This causes a delay of 8 seconds before my data field view is updated and my algorithm is called again. Unfortunatly, sometimes the delay happens after my algorithm could recognize the LAP and sometimes before my algorithm could recognize the LAP. The latter case leads to the problem, that my lap timer starts with a delay of these 8 seconds. I have implemented a hack that seems to work stable.

@GARMIN: PLEASE ADD LAP TIMER ACCCESS FUNCTIONS TO YOUR API.

VERSIONS
========
0.01 First version
0.02 Small bugfixes
0.03 Small bugfixes
0.04 Unit added to Total Timer display

INSTALLATION
============

After Downloading with Garmin Express you have to set the view as single data field.

- Long Press Menu/Up Key
- Select Settings
- Select Activity App (Run)
- Select Data Screen
- Select Screen 1...10
- Select Layout
- Select Single Field
- Select Field 1
- Select Connect IQ Fields
- Select Bold Data