DataFields : 367 RunFields

Update 2015-09-15

Have started to upload V2 of the 367Bike and RunFields to the App store.
367BikeFields is Live.
367RunFields is Live

The new version adds TimerTime, also adds the seconds on the timer once you reach > 1hr. (I'm told that seeing seconds is especially important for runners)

Note for all : Please refer to the app store for the latest in the NEW direction the app/datafield is going.
Go PRO! GO UnLimited!!

TOD (Time Of Day)
Timer Time
Pace 10s / Current Speed (in KM or Miles)
Cad
HR
Dist (either Miles or KM)
Avg Pace / Avg Speed

Nikeow over 10 years ago

if (width == 205 && height == 43)
if (width == 205 && height == 57)
if (width == 205 && height == 44)

That's what in the code.by right they should be right for the VA.

can one of the connectIQ guys let me know what's happening?

Former Member over 10 years ago

The bottom field on the device is defined with a height of 43, making the bottommost row of pixels unavailable. I've created a ticket to look into making sure the layouts match between the device and simulator.

In general, I would not recommend defining behavior based on the width and height of a data field device context.

Nikeow over 10 years ago

Thanks Brian for clearing that up.
That being said - can u provide me with a recommendation as to how one would be able to properly code for the associated devices with the different layouts?

I tot I could use the obscurity mode, but looking into the devices.xml files doesn't indicate or if memory serves right, has a unique obscurity mode to properly determine that the device is a VA.

Are there any samples in the SDK which would be able to help?

Former Member over 10 years ago

The best solution is to use application settings to configure the data the user wants to see, but we haven't released that feature yet.

You are attempting to implement three different feature sets with a single application. As it stands right now, this should probably be 3 different applications since the configuration feature isn't available.

DigiDAD over 10 years ago

Looks good - confirmed working on VA @ FW2.70. Again, only 2 ConnectIQ fields are suported on VA, so no real option for the 9 field display.
Hope one day they update firmware to to increase that to 3 ConnectIQ fields per data screen.

Nikeow over 10 years ago

The best solution is to use application settings to configure the data the user wants to see, but we haven't released that feature yet.

You are attempting to implement three different feature sets with a single application. As it stands right now, this should probably be 3 different applications since the configuration feature isn't available.

Ah... Okay.
Note that I understand the restrictions and I unfortunately didn't realise that when I was coding the support (since the 920 and the F3 has the 1 single large datafield support).

But after Manuel tested it and provided that feedback, then it makes sense that the app, in its current state, does offer the person the option of deciding which fields he/she wants based on current restrictions.

Like Manuel demonstrated-he was successful in configuring the diff layouts (with exception of the 3rd row)
Anyways - the 3rd row are all averages - I only added that cos there was space. No biggie. Don't think lots of people are interested in averages during their ride/run anyways.

Cheer.

Nikeow over 10 years ago

Looks good - confirmed working on VA @ FW2.70. Again, only 2 ConnectIQ fields are suported on VA, so no real option for the 9 field display.
Hope one day they update firmware to to increase that to 3 ConnectIQ fields per data screen.

Doesn't really help me nor u even if it does unless whatever Brian said is a reality (application settings). Can't do 3 anyways based on current sized based layouts.

Former Member over 10 years ago

Used it last night, one of the best data fields out at the moment.

Only comments, could a new version be created with

1) "Elapsed" changed to "Timer", so that you can pause the watch and just see the time actually running.
2) "Last Lap Pace" displayed instead of HR so it works well for Interval training or just checking your last lap pace.
3) Maybe Cadence changed also but can't think of another useful one.

Thanks.

Nikeow over 10 years ago

Used it last night, one of the best data fields out at the moment.

Only comments, could a new version be created with

1) "Elapsed" changed to "Timer", so that you can pause the watch and just see the time actually running.
2) "Last Lap Pace" displayed instead of HR so it works well for Interval training or just checking your last lap pace.
3) Maybe Cadence changed also but can't think of another useful one.

Thanks.

If not mistaken - #1 and #2 is not exposed by the API and thus needs some level of manual calculations. I've not reached that level of proficiency :-)

DigiDAD over 10 years ago

If not mistaken - #1 and #2 is not exposed by the API and thus needs some level of manual calculations. I've not reached that level of proficiency :-)

How difficult have you found coding in this Monkey C? Are there source code sample projects for things like data fields. I did some C++ coding back in college and other scripting since. The data fields I am interested in are all available data, just want more of them on-screen than the 3 my vivoactive allows natively. I have been running with yours this week, but find the small fonts in the top bar too hard to read. Once you develop stuff, is it easy to sideload without publishing?