What's the error you see? If it's from type checking, use ORDER_NEWEST_FIRST or ORDER_OLDEST_FIRST and not a Number for order
You can walk the iterator and count them. You may find you have two cases where you use the info from SensorHistory.get*History - you either want only the newest sample, or you want to graph what's there…
Well i can say that the fenix 5 has 180 samples for temp, press and elev but only 120 for Heart Rate...
Turn off the f5 turn it back on, and check again. You'll see far lower numbers.…
I've been doing CIQ since it came out, and things like SensorHistory since it was introduced. And sometimes code things a bit different than what I see in the API doc, based on experience. I'm still not sure why you think you need the history length. You just need to graph how many you find and stop when your graph is full. If you want min/max for scaling, use
min=iter.getMin();
max=iter.getMax();
right after line 2 in the code I posted. It may be a bit off based on the number of samples you use, but still in the ballpark.
I will check min & max from iterator tomorrow. Actually i extract min & max from the collected data for scaling. I want to add a setting about the number of samples to display. This number can be changed by user…
Your file isn't available on windows/chrome.
Let the user set a number, but consider that a max, as you can have fewer samples based on when the user turned on their watch,
Yes, i count the hist length, i check user setting for max num of hist samples he likes, create an array of user-max-value length , filling with zeroes if hist has not enough samples .. et voila!! :-)
the app is updated on the store!! I woukd like to thank you for the effort and for the time you spent answering me!!