Data field: Visual Pace Alarm

Former Member over 9 years ago

The Visual Pace Alarm data field is a visual aid to help you keep your pace. Visual Pace Alarm shows your current pace and uses a gauge or a background color, depending on the size of the field in which it's placed, to show you how close you are to the pace you've set.

You can find the data field here.

*********** Features ***********

You can set it to show your current pace or the average pace over a set number of seconds;
Pace gauge, if displayed on full screen (fr920xt / epix) or at least upper half screen (all (semi-)round devices);
Pace zone as a background color for all other sizes;
Allows you to set target pace and allowed offset to that pace. Offset in both directions is split into 5 zones, that are color coded Yellow, Blue, Green, Orange and Red.
Pace gauge view flashes background on leaving target pace zone.

*********** Requirements ***********
Connect IQ version 1.2 or above

*********** Version history ***********
v1.0: Initial version

*********** App Settings ***********
General information about app settings can be found here.

The settings:

Target Pace: the pace you want to keep
Number of seconds to outer limit: the data field splits the pace between target pace +/- outer limit in 5 zones that are displayed in different colors
Number of seconds pace average (optional): you can get direct response if set to a low value or maintain an average over a larger period.

Some screen shots:

Former Member over 9 years ago

Visual Speed Alarm is similar to Visual Pace Alarm, but it shows speed instead of pace.

You can find this data field here.

Some screen shots:

PatFelstead over 9 years ago

Very attractive design TeunMo - well done. I will try it out this weekend.

Former Member over 9 years ago

Very attractive design TeunMo - well done. I will try it out this weekend.

Thanks! I hope you'll find them useful.

GSparky over 9 years ago

Vivoactive

On vivoactive all I can get is a text field.
Is the gauge not available for this watch?

Former Member over 9 years ago

On vivoactive all I can get is a text field.
Is the gauge not available for this watch?

Unfortunately on the vivoactive it's only possible to select a data field with 1/3 of the screen height. This is to small for the gauge, so it switches to the alternative view. In that view it doesn't display a gauge, but it does set the background color to indicate whether you're in the right pace/speed zone.

huubraemakers over 9 years ago

Pace zones?

Nice app, maybe the following is also possible? Would be very nice for training.

I would like an app like the Visual HR zones, but then with pace zones. For instance:
- Zone 1: Active recovery - >6:26

- Zone 2: Endurance - 6:26 - 5:32

- Zone 3: Tempo - 5:32 - 4:58

- Zone 4: Threshold - 4:58 - 4:39

- Zone 5: VO2max - 4:39 - 4:23

- Zone 6: Anaerobic - < 4:32

Hope this app can be made by you?

Best regards
Huub

Former Member over 9 years ago

Based on what I already have for this data field, it's not difficult to create what you're asking for. I'll think about it.

Former Member over 9 years ago

Gauge also on bottom half of round screen?

Hi,

I love this data field, and also your other data field "Heart Rate with Zone". I have a Fenix 3 and the most useful layout for me is to have both of these data fields on one screen. For some reason I prefer to have "Heart Rate with Zone" on top and "Visual Pace Alarm" on the bottom. Everything works fine, but like you state it since "Visual Pace Alarm" is not on top, it'll switch to the alternative display with just the value and background color based on how close to the target pace I am.

I'm thinking though that since the bottom half of the screen has the same size as the top half, and it would be a lot nicer to have the gauge for both of these data fields, would it be possible to detect "bottom half" just as "top half" (of round screen) and for "bottom half" do an "upside down" (or "mirrored") gauge?

If this isn't too hard and you decide to do it, maybe it's a good idea to do it for "Heart Rate with Zone" as well, since others might prefer to have them arranged the other way around?

Thanks a lot,
Mattias

Former Member over 9 years ago

Hi,

I love this data field, and also your other data field "Heart Rate with Zone". I have a Fenix 3 and the most useful layout for me is to have both of these data fields on one screen. For some reason I prefer to have "Heart Rate with Zone" on top and "Visual Pace Alarm" on the bottom. Everything works fine, but like you state it since "Visual Pace Alarm" is not on top, it'll switch to the alternative display with just the value and background color based on how close to the target pace I am.

I'm thinking though that since the bottom half of the screen has the same size as the top half, and it would be a lot nicer to have the gauge for both of these data fields, would it be possible to detect "bottom half" just as "top half" (of round screen) and for "bottom half" do an "upside down" (or "mirrored") gauge?

If this isn't too hard and you decide to do it, maybe it's a good idea to do it for "Heart Rate with Zone" as well, since others might prefer to have them arranged the other way around?

Thanks a lot,
Mattias

Hi Mattias,

Thanks for the feedback. I'll look into this, but I can't make any promises. For a data field there's a limited amount of memory available and for both of these data fields I've used almost all of that, because of all the different layouts that are already supported. This means I have to be careful in what to include and what not to include. Mirroring the layout is not difficult, but it does mean recalculating a lot of variables and this will use up quite a bit of memory.

Former Member over 9 years ago

Hi Mattias,

Thanks for the feedback. I'll look into this, but I can't make any promises. For a data field there's a limited amount of memory available and for both of these data fields I've used almost all of that, because of all the different layouts that are already supported. This means I have to be careful in what to include and what not to include. Mirroring the layout is not difficult, but it does mean recalculating a lot of variables and this will use up quite a bit of memory.

Thanks for your extremely fast response! :D

And thanks for explaining the limitations! I understand that you're put in a tight spot by them. Maybe this is a crazy idea (I have no clue how much hassle or overhead there is for each app or data field), but would it be possible to maybe split the delivery into a couple of separate deliveries for different layouts? That way at least each version would require less memory… I realize that some users might be confused because they expect to install just one thing and then configure it or have it behave and adapt automatically, but since the execution environment puts limits on you maybe it could be something to consider anyway, as a form of workaround to break out of some of those limits?

Cheers,
Mattias