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

 

  • como hago para ponerlo en el garmin 1030 cuando lo tengo hecho.

  • I'm a software developer for technical software (e.g. for railway solutions) - and we use "real" UTF-8 formatted XML everywhere. IMHO there's no need to store the special characters as "&#186" (or "ü" für "ü" and so on) - that would only be necessary if you use the files e.g. in a web browser. And without that changing it should be no effort at all - just the "simple" thing to find the correct parameters for the file writing and reading methods...

    But you're right - I don't know, if the Garmin devices can show the UTF-8 special characters at all.

    BTW, I tried to use the "arrow up" and "arrow down" characters - now I "painted" some with lines...

    @hundsmiachn: and if you decide to keep the current ANSI format, you should at least remove the "UTF-8" from the XML header - that confuses some tools...

  • 4:) that would be nice - maybe additionally also some kind of valuetype (e.g. 1 for day, 0 for night)

    6.) you're both right - it's not really necessary...

    3.) I don't understand your answer....
    if I understand correctly, there is a) always a  dynamic color necessary if you want to set limits for dynamically sizing graphical elements? So e.g. if I want a black rectangle be unfilled (and keep at that) between 0 and 10 km/h speed and have 100% filled at 45 km/h and above I have to set a dynamic color value to black with  value 1000 and a second value also with black and value 4500?

  • Hi

    I will change to format of the xml file utf-8 so it matches with the header. I think that garmin devices only support a specific char set, so that special characters won't be drawn anyway.

    Your values would need to be 100  (for 10km/h) and 450(for 45km/h). So, no rectangle will be drawn until 10km/h and it will be 100% drawn at 45km/h. I you dont want a color change just set both colors the same.

    regards

    Erich

  • No, you need not use the code for „ü“, but you‘ll need it for „extended characters“ like your arrows or you will get an error not only on browsers but also on XML-editors. BTW - you also need the code for „<>“ although this are not extended characters, but are reserved for tags.

    Out of curiosity I did some testings: Using the Windows Character Map (Zeichentabelle), it seems our Edge can show all characters listed in „Arial“ and „Windows Western“ table. And all these characters are stored well (and reopened) in DIY. I dont‘t know if that also depends on Edge‘s language setting to German...

    Then I copied the „arrow up“ sign from the character map (Arial Unicode) and pasted it into the definition string (Setup) between existing text. I think with „normal characters“ this would be a possible way - but with „arrow up“ this character is not shown on the device (although the character ist stored correctly and is here after reopen in the setup-routine).

  • Hi, I got the program but I can,t work with it because in my laptop the bottom is cut. I know people with the same problem. They only can work with a PC. Do you know any solution?

  • Hi

    For now there isn't really a solution for this, sorry. But I am working on a new version and will keep that in mind.

    What is your screen resolution?

    regards

    Erich

  • Not sure if this is the same issue I had trying to use on a 4K monitor, but doesn't hurt to try this fix.

    Right click the exe, click properties, click Change High DPI settings, check High DPI scaling override, and chose SYSTEM from the drop down, back out saving. This worked for me on a 4K monitor where the image of the device would show up UNDER the text. Might work, might not:)

  • Hi

    I tried it with 1280x960 and it still fits on the screen. Do you use a lower resolution?

    One thing you could try:

    * Close the designer

    *Open regedit.exe and delete all values under \Computer\HKEY_CURRENT_USER\Software\MiachSoft

    * Reopen the designer again

    regards

    Erich

  • I,m afraid, I must Walt for a new versión. My resolución is 1366 x 768.