HMs DIY #1-6

Store Link

Because I want to keep this datafield and the app free for use I would be very grateful about a small donation to PayPal

A detailed description of how to use it can be found here: 

HMs_DIY_GUIDANCE.pdf
HMs_DIY_ANLEITUNG.pdf

Thanks very much to mcinner1 for putting so much time into this documentation!

Designer download

You can contribute on my github page.
You can upload your layout so others can use it as well.
Also any changes to the fonts.txt can be updated there as well.

Garmin_HMsDIY

=======================================================================
RELEASE NOTES
=======================================================================
-----------------------------------------------------------------------
3.6.2
* switched to new SDK 7.2.1
* added devices: Approach S7 42mm, Descent Mk3 43mm /Mk3i 43mm, Descent Mk3i 51mm, Edge 1050, epix Pro Gen2 42mm, epix Pro Gen2 47mm / quatix 7 pro, epix Pro Gen2 51mm / D2 mach 1 pro / tactix 7
Fenix 7 Pro, Fenix 7 Pro Solar, Fenix 7S Pro, Fenix 7X Pro, Fenix 7xPro Solar, Forerunner 165, Forerunner 165M, Venu 3, Venu 3S, Vivoactive 5
-----------------------------------------------------------------------
3.5.1
* switched to new SDK 4.2.4
* added devices: FR265, FR265S, FR965, GPSMAP 67/67i, Marq (Gen 2), Marq (Gen 2) Aviator, EDGE 540, EDGE 840, Instinct 2x Solar
* added two new font types GLANCE, GLANCENR (only available if device supports it!)

for full releasenotes see: releasenotes.txt
=======================================================================

 

  • Hi

    Thank you very much, really cool layout !!

    Didn't think myself that this is possible with only 5 types of graphic elements.

    Thanks for your testing and fast responses.

    Unless there is a major bug I will release a new version in a few days with most of the points from my todo list.

    If there are any more wishes for values or features please post it here.

    regards

    Erich

  • If there are any more wishes for values or features please post it here.

    Hahaha! You'll regret saying that because of all the wishes you will get!
    Grinning

  • Hi Erich

    What I miss the most is

    • Values for last lap
    • Pacer functionality (+/- target pace set in app with gained/lost time due to off pace)
    • Distance left to some set distance (in app - what the original DIY did with multiple distances was really nice) and expected time to the target distance set in app.
    • A "graph" field  would also be nice (HR/pace/etc)
  • Hi

    I think distance left is already available, it should be "distance to destination" and "distance to next point", including time to XX and ETA.

    regards

    Erich

  • I had today with my Forerunner 945 extreme battery consumption - 8-12% per hour (8% by running with 1 variable with dynamic coloring and 12% by cycling with 2 variables with dynamic coloring), normally was 4-5% per hour. Had someone that experience? What can be a reason for this? Thanks.

  • Hi Thanks for offering some solutions. I hadn't spotted the 2-stroke, like you suggested it was originally cloned from a 2-stroke line, but once it was changed to a filled rectangle the stroke couldn't be changed. 

    I recreated the rectangle with 1-stroke but the issue still occurs. Also as you alluded to, the element is disappearing not simply turning black as the red highlight disappears when I increase the size of the rectangle

    Here is a link to the XML if you have time to check it out: layout_Edge1030.xml It's still work in progress as a couple of the timer functions haven't been released as yet, so I was just testing the layout for when they are

    Note for . I'm not sure if the Left/Right alignment is working correctly. I originally added a left aligned % text element to a right aligned battery percentage in my layout above and positioned it as can be seen in my layout. However when it was loaded on to the edge the % symbol was positioned further left and was on top of the battery percentage value.

    Also, not a bug, more cosmetic with the 'Name of next point'. If there isn't a course loaded or the loaded course doesn't contain any course points the field displays 0.0. Maybe at some point in a future release if there is no data for that field it could be made to be blank 

  • I‘m out and will check your XML on Sunday afternoon!

  • Hi

    I tried you layout and couldn't reproduce your problem. But I changed the behaviour of the clipping area, I hope this fixed the problem. I will release a new version later today. 

    regards

    Erich

  • Hi

    I have to admit, I did not test the battery consumption with my datafield. Is it possible that you do 2 identical runs, one with my datafield and one with a standard one, so we can narrow down the problem (with same devices attached and same gps settings) ?

    thanks

    regards

    Erich

  • New version 1.1.7 is out!