HMs DIY #1-6

Ok!

Will try tomorrow (now it's near midnight here in Austria)

Good night!

In Denmark, too :-)

Goodnight.

Hi

@hotdogpartysausage: if you mean with elapsed time, the time since the activity has started, this is "timer time". I will rename it as I think too that it is a confusing name.

Added current lap time to my list.

Dynamically coloring fixed text is a little bit trickier, but will try to add it.

Adding text to time fields already works, will try to extend it to all value fields.

I added a clipping rectangle around every devices visible area, I will extend it by 2-3 pixels, I think this is the problem with the rectangle.

regards

Erich

There is a new version 1.1.5 for the datafield!

mcinner1 found a bug where the datafield crashed when using time to destination.

Because of the memory optimizations in the last version I had to rework a part of the code and there I had a little typo which caused the crash. But should be fixed now!

regards

Erich

fjelsten
After a little interlude I have now tested your layout on my Edge.
However, I had to make some changes to your XML
I couldn't load your layout originally. (Yellow Triangle of Death!)
"Nr of values" was set to 2 for several text elements and unnecessarily for value elements.
I don't know if this was the only fault.
So the layout shown doesn't quite match yours.

"Time to Dastination" is displayed correctly!
By the formatting $M:$S however in minutes - 107:13.

Hi

I have found a problem with the values for nextpoint and destination. I simply forgot to decrease by elapsed distance )-:

Will be fixed in next version!

As this isn't a blocker bug I will wait a while for the next release.

EDIT: I dug a little into this problem and it seems that the SDK is providing wrong values for distancetoDestination and distanceToNextPoint on some devices.

I dont know if the values should be decreased by the SDK or me, but from the name I would expect that the value is decreased automatically, also for next point because I dont know where the last point was, do I?

I dont know what the values should be and how to calculate them.

regards

Erich

Due to the optimizations one more thing came up, performance issues. So I had to revert some of the changes to get rid of this issues -> thus I uploaded a new version 1.1.6

Sorry for that many updates, but monkey C coding with this limited memory is a pain in the a...

lg

Erich

I really appreciate all your work.

As Erich writes below I expect it's an unit issue.