Data field: Snapshot

I like this data field a lot. Worked great yesterday, but today I am getting the IQ! Symbol instead. Any suggestions?

I like this data field a lot. Worked great yesterday, but today I am getting the IQ! Symbol instead. Any suggestions?

This seems to happen when you move from the data field back to the watch face then to the data field again, all quite quickly. The watch appears to fail to load some of the settings for the field when doing this and hence returns an error. It doesn't happen when you just select and use it normally; just when you jump back and forth between watchface and field too quickly

It's easy to fix though: go to your activity screen settings and select it again. Let me know if this works.

I've been trying to figure out if the crash is a subtle code issue of mine or a watch "feature" that i have to guard against. It's a strange one for sure.

The code for Snapshot is now publicly available at https://github.com/darrencroton/Snapshot

v1.1 is now available:

+ Fix for average cadence, where CIQ was reporting half the actual value

I'm still having problems running this data field. Your fix doesn't appear to work for me.

Sometimes I can get it working by uninstalling/reinstalling, but once I go into the fields settings, from GC mobile, it errors out again.

I'm still having problems running this data field. Your fix doesn't appear to work for me.

Sometimes I can get it working by uninstalling/reinstalling, but once I go into the fields settings, from GC mobile, it errors out again.

OK. I can't reproduce the crash myself so let's dig deeper. Can you tell me:

• What watch you're using (230, 235, 630 or 735XT).
  
• The version of your firmware and HRM (if relevant) - go deep into settings and find the "about" menu item.
  
• From the watch face and with the field freshly installed, exactly the button presses that produce a crash.
  
• Does opening the settings from GC mobile then hitting save without changing anything cause a crash?
  
• Does it crash only when you go to start an activity or crash while still within the activity screen settings?
  

Hopefully we can figure it out.

Adding distance?

Thanks for an excellent data field. Would it be possible to have distance selectable as an alternative for the time-of-day and battery remaining? That would be awesome for races where you don't care about the time-of-day and having charged the watch fully just before.

A single race data screen like this would then be possible:

1st line: immediate measurements Heart Cadence
2nd line: pace measurements Lap pace Avg page
3rd line: summary/total measurements Timer Distance


Best rregards,
Mikkel

Thanks for an excellent data field. Would it be possible to have distance selectable as an alternative for the time-of-day and battery remaining? That would be awesome for races where you don't care about the time-of-day and having charged the watch fully just before.

A single race data screen like this would then be possible:

1st line: immediate measurements Heart Cadence
2nd line: pace measurements Lap pace Avg page
3rd line: summary/total measurements Timer Distance


Best rregards,
Mikkel

Thanks Mikkel. Let me have a think about how i'd implement this.

I could add an option to replace TOD+battery with distance using the same font as the timer, which would be nice and readable (especially during the effort of a race). But i think the horizontal space on that side will allow only 3 digits plus the decimal place (e.g. 1.23, or 10.3), or maybe even only 2 plus the decimal (e.g. 3.5).

So i would probably need to use the smaller font that's currently used and put the distance in the top line where the TOD is, or maybe centre it vertically. If replacing the TOD, the battery spot underneath could be used for something with a maximum of 3 numbers, like an additional HR or cadence field (ave HR or ave cadence, say).

What do you think?

Unfortunately in this lower quadrant it's all about what can fit for all reasonable distances (XX.YY km or miles) and times (hrs:min:sec), without looking cluttered and still being readable (i.e. not going smaller than the smallest font currently used).

Thanks Mikkel. Let me have a think about how i'd implement this.

I could add an option to replace TOD+battery with distance using the same font as the timer, which would be nice and readable (especially during the effort of a race). But i think the horizontal space on that side will allow only 3 digits plus the decimal place (e.g. 1.23, or 10.3), or maybe even only 2 plus the decimal (e.g. 3.5).

So i would probably need to use the smaller font that's currently used and put the distance in the top line where the TOD is, or maybe centre it vertically. If replacing the TOD, the battery spot underneath could be used for something with a maximum of 3 numbers, like an additional HR or cadence field (ave HR or ave cadence, say).

What do you think?

Unfortunately in this lower quadrant it's all about what can fit for all reasonable distances (XX.YY km or miles) and times (hrs:min:sec), without looking cluttered and still being readable (i.e. not going smaller than the smallest font currently used).

Thanks for the prompt reply. Yes, I see, it's really a delicate balance between information density and legibility. I think your suggestion of using the same font as the TOD and then using three digits, e.g. 21.1 km or 13.1 mi or 1.23 mi, would be perfect. And maybe the battery space is fine to use for a label for consistency with the other fields? But I acknowledge that others may want an extra field.

A side note: I personally do not find avg cadence or avg heart rate very operational, as it is not something I would try to overshoot with just to reach a certain goal of e.g. 180 SPM or say 160 BPM. For me it's more something that you monitor on-the-fly and correct as needed. Adding 15 BPM for a while in order to reach your desired average doesn't strike me as a particular good idea :)

Another totally awesome thing: what if the Heart Rate label dynamical could have the current zone appended? As in Z1 / Z2 / Z3 / Z4 / Z5. And, and, and, (no I'm getting carried away), what if the background of that field could reflect the zone as well, using the same colors as in 'official' heart rate page? That would be very 'glanceable'. Well, I'll stop now with all the good ideas :)

But one final thing: I looked a little at the SDK. How long will it take one already skilled in programming to get started with making own data fields? Not that I really need new hobbies, or have to much time on my hands, it just seems so tempting....

Best regards,
Mikkel

OK. I can't reproduce the crash myself so let's dig deeper. Can you tell me:

• What watch you're using (230, 235, 630 or 735XT).
  
• The version of your firmware and HRM (if relevant) - go deep into settings and find the "about" menu item.
  
• From the watch face and with the field freshly installed, exactly the button presses that produce a crash.
  
• Does opening the settings from GC mobile then hitting save without changing anything cause a crash?
  
• Does it crash only when you go to start an activity or crash while still within the activity screen settings?
  

Hopefully we can figure it out.

Hi

This looks great, but I have the same issue, it does not seem to be about swapping to the face, but rather on altering the settings (specifically changing lap pace to current pace, but probably for all settings). Selecting it again does not help. Rather you have to reinstall and remove other things to get it to work again.

1) 735xt
2) software 3.3. Connect it 1.2.5. Optical HRM
3) going directly to activity screen, menu, activity settings, data screens, screen 2, selecting single layout, adding to field 1. Works. Then altering a settings, syncing and doing the same gets 'iq!'.
4) clicking 'done' without changing anything does not seem to have an affect. Changing a setting (invert) and changing it back and then clicking 'done' does seem to apply then. This does not cause it to crash.
5) crashes at the data screen setting screens already.