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
=======================================================================

 

  • What Valuetype have you assigned to the item you are trying to change the colour for? It cannot be Fixed Text.

    Also does the colour to replace setting in the dynamic colour match initial colour you have assigned item you are trying to change the colour for. 

    It might be worth posting the XML file, which would aid pinpointing the issue.

  • Here the links to the layouts:

    Layout1 with one dynamic color works fine.

    drive.google.com/open

    Layout2 with one other dynamic color works also.

    drive.google.com/open

    Layout3 with this two dynamic color fields get an iq error

    drive.google.com/open

  • Hi

    You have simply run out of executable code lines on your device. This means too much elements!

    You will have to remove some elements. Not every device has same memory and number of code lines.

    for example: the max number of elements on my FR935 is about 25.

    regards

    Erich

  • New version 1.1.8  (Designer only) is out.

    The fonts.txt file has changed! Instead of one X Offs you can set now 3 Offs (for every alignment).

    So, if you have edited the fonts.txt yourself, you will have to adapt it, otherwise it won't be loaded anymore!

    regards

    Erich

  • Thank you. Thank you.
    Sh@*#t, I'm on 3 days vacation and can't try out immediately. Disappointed

  • Today I made two tests by simultaneous use of FR 935 and 945:

    By cycling 1 hour 8 minutes with HM-DIY on both and than 1 hour 8 minutes with native Garmin screen on both. On FR 935 no difference in battery consumption however on FR 945 12% with HM-DIY and only 7 % with native Garmin screen. No dynamic elements on HM-DIY. My HM-DIY hat 15 values. Less battery consumption hat FR935 (but 945 should be better!).

    The second test by running, using HM-DIY running Layout with 1 dynamic element. I have 11 elements in my layout (less than for cycling). And the battery consumption was similar by both FR 935 and 945, and better than by cycling.

    So I think the number of elements influences the battery consumption.

    I have used the 1.1.7 version of Datafield and Designer.

  • Finally had time to test the new version. The Name of next point seems to be sorted thanks.

    I'm still fine tuning the left/right justification offset but they seem to be working as intended.

    I think the only outstanding issue I have is with the Elapsed Time formatting

    I noticed that it isn't possible to have 0 as a Dynamic colour value & was wondering if this could be a possible future addition.

    Will hopefully get chance to test in anger at the weekend and see if there's significant impact of the battery life whilst navigating

  • Hi

    I will release a new version of the datafield today, so the elapsed time should then be formatted ok.

    For dynamic colors: you can use 1, that should be a value of 0.1. Why do you need 0 as a value?

    regards

    Erich

  • Hi

    Thanks for your testing.

    To be honest, I cannot really do much about that. I already optimized as much as I could. Dont see any code which would use so much performance that it drains the battery more than usual. I think it is just the number of elements. Any simple datafield has only 2-3 values to be drawn, not much graphics and value averaging so they use less battery I suppose.

    regards

    Erich

  • I made layouts with lees values and anw it's ok.

    Can you by Distance-Values add the possibility to have under 100 km Precision 2 (xx.yy km) but after 100 km Precision 1 (xxx.y km)?  Thanks.