Fenix Data Field Limits

I look for obscurityFlags = 0 to identify a rectangular field (eg: EDGE devices). GREAT idea about those add'l stats. I'll apply those. THANKS!

Time for another silly question.....

When you say the watch only allows 2 custom datafields....... I am finding if I open my single custom datafield, 4 of the 6 values I am trying to view are displayed as 000000000.0 ...............it appears that  two custom datafields means two custom datafields on screen at once if you are viewing a datafield?

Two CIQ data fields per activity.  You can have two in "run" and two different ones in "walk".  As far as the 4 bits of data in a single DF being zero, sees that the data you are trying to display may not be available for the activity type, or you're displaying some navigational data but you're not doing navigation.

I don't think so, I'm using navigate app, and when I pulled the exact code that's displaying 0.00000 and put it on its own Data field, it displays correct.

With the rest of the values, 0.000000

Are there limits we don't know about for number of Data field values allowed to calculate? 

There's no limit on how many things you can calculate, with the exception of tripping the watchdog timer (your app will crash).

if the code works in one DF but not in another, there's some difference between what you do in the two DFs.  In the DF where you get 0.000000, try commenting out code until it works, or in the DF where it does work, add things from the 1st DF until it breaks.

Nick - remember that it depends where you calculate stuff. in a DF, compute() runs every second (about), even in the background when you are viewing another screen that does not include your DF. In the simulator, you can't push your DF off screen, so it always runs. On a watch, of course, you can push your DF off screen... and if you are performing your calculations called from onUpdate(), for example, the calculations won't run until you bring that DF back into view.

All of the caclulations I am getting from activity.info are calculated and assigned to variables within compute ().

Variables are initialized outside compute ()

I have about 6 different onCompute activity.info methods that are being used..... which is making me think is there a limit of 2 of these being able to be called on the watch??  that would explain why the other 6 fields are blanked.

I will disable the fields that are showing correct, to see if any other fields then stat showing correct to confirm my suspicions

The only other difference in the code, is that i've deleted layouts, and I am only using DC draw in my datafield VS when I tested the code seperately layouts was still there. I never exited the datafield, as it is what I wanted to view.

There's no limit on how many things you can compute in a single DF.  Look in the store, as there are some that display 10-12 things at one time.

Try putting some println calls in your code and then on the watch, create  a <myprgname>.txt file in the logs directory to see what's going on.

Thanks Jim, and Dave, I think I have fixed the problem and potentially found a bug

The problem was activity.info.bearing, and activity.info.track;

the API docs state that these two values were Radians, but it doesn't state that North = 0. So West = -90 and East = 90.

When I use Math.toDegrees(info.bearing) side loaded onto my watch it converts the -1.4 Radians to -90 or so degrees, and not a compass degrees.

The Peculiar thing is; in the Fenix 6  watch simulator, Math.toDegrees appears to convert the track to an actual compass track out of 360 for some reason.

On the actual watch it does not - I don't know if it's a bug or not?.  The input radians are definitely +- 0 with 0 = North.

Do a bug report in the CIQ Bug Report forum.  Include sample code to demonstrate the problem.