I've been working on a data field similar to ones that have become popular on the IQ store recently that has multiple pieces of data with various fonts. I'm working on it for my own use for hiking to have more than 4 pieces of data on the screen. The obvious data like battery level, time of day, distance, speed, elevation, etc were all straightforward. I would like to also have some of the navigation related data such as distance remaining, ETE, ETA, etc. I'd also like to have the temperature from internal or tempe. Am I correct in assuming that this navigation related data and temp data are not available to a datafield in the current APIs? I'm not particularly interested in doing this in a widget because I'd rather have it in the usual screen stack while in the activity.
The Sensor.Info type contains a temperature field, but the Sensor module is not supposed to be available to data fields. I find this vexing because the Ant module is available and you can get access to the Tempe data if you were to write all of the appropriate code.
You might write a bit of test code to see if Sensor.getInfo() is accessible and see what is in the Sensor.Info if it is.
The Sensor.Info type contains a temperature field, but the Sensor module is not supposed to be available to data fields. I find this vexing because the Ant module is available and you can get access to the Tempe data if you were to write all of the appropriate code.
You might write a bit of test code to see if Sensor.getInfo() is accessible and see what is in the Sensor.Info if it is.
Travis
Or, if Temperature was available in Activity Info (like HR, cadence, etc) there would be no need to get it from Sensor Info.. That could be a ways out, I'd guess....
The reason Sensor isn't available to data fields is because you're already getting an Info object from the Activity module. That said, Activity.Info doesn't quite provide all of the basic info provided by Sensor.Info. Temperature is one omission, and I'm not certain of the reasons. It's likely because temperature isn't available to all devices natively, but that seems like a good case for "has" to me. I'll file a JIRA and see if we can't bring the two Info object types a little closer together.
How about the navigation related data like distance remaining, ETE, and ETA? Am I missing something, I didn't see these as part of the Activity.Info either.
How about the navigation related data like distance remaining, ETE, and ETA? Am I missing something, I didn't see these as part of the Activity.Info either.
Those seem like things you need to calculate yourself. Or do you need the location you're "going to" to calculate that? That's a different question...
I guess i was optimistic that these pieces of data would be accessible without doing any sort of calculation. I wouldn't care to recreate these sorts of calculations since in this case i'm typically doing a course and you'd have to have access to the course data and take into consideration the distance along the track/route as well as the current speed.
I am absolutely convinced that Activity.Info must contain all the values that you can select for the fields on built-in screens. I realize that the calculation of all of them and writing to Activity.Info can be time consuming and mostly unnecessary, because usually is used only a few values. Accordingly, I propose that the Activity had static function e.g.: getValues(array_of_symbols) which will contains the symbols of values that are to be calculated. At the end of Activity.Info there will be similar table with calculated values (recorded in the order of symbols in array_of_symbols).
I have already requested that we expand Activity.Info to include the items it doesn't already cover that are available in Sensor.Info. It's on the road map.
Expanding Activity.Info to include other items like ETE, etc., is another matter. I'll file a request to have it considered, though, and we'll see where that goes. I think it would be nice to include all of the selectable fields, but there may be technical reasons why these weren't included that I'm not aware of.
I was wondering if there had been any further talk or progress of making the data from native screens available in activity.info? I'm especially interested in ETE, ETA, and Temp.
I was wondering if there had been any further talk or progress of making the data from native screens available in activity.info? I'm especially interested in ETE, ETA, and Temp.
Things like this don't move fast, as even if it's approved today, it wont be available until sometime in 2016, and it would likely be a SDK "2.x.x" thing which is probably still a way out (maybe 2+ months)
