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

 

  • Ok, thank you. I am sorry for the problems... 

    Regards 

    Erich 

  • Thanks  &  for your investigation & development work. I can confirm that the adjustments to the clipping in 1.1.7 of the designer solves my screen issue. Happy Days Slight smile Maybe the issue on my system had something to do with font scaling or display resolution on my laptop. I'd overridden DPI scaling in the executable following previous layout issues but maybe there was something that wasn't quite right. 

    Nice work on the alignment checks. I agree that it's easy to account for in the design so not worth any additional layout offsets. Actually for me the new formatting feature in 1.1.7 pretty much removes the need for left/right justification to align with units text as I can now put them all in the same field.

    Looking forward to trying out the new features in my layout. I think I've got pretty much all the data values I need to keep me going for a while. Thank you

    EDIT: I've just uploaded my layout to my device. There's a couple of little issues with the new additions; the Elapsed Time $h:$m:$s formatting doesn't appear to be working as it displays $:$:$ in the field (Timer time & Current lap time seem to be OK) . Also the Name of next point is displaying Eribor in the field all the time


  • And, by the way, a nice new icon!  Grinning

  • Hi

    Forgot the elapsed time formating to be a time, will fix that. As for the name of next point: It should not export the dummy name thats a bug, but it should replace it in the datafield if there is a next point name set. Does name of destination work?
    Strangly in the simulator I cannot reproduce it. Could you post your xml file? I suppose it is a problem in the SDK, as there are several bugs which are not fixed yet regarding next points and destination.

    regards

    Erich

  • Today I was running, my Datafield hat 1 dynamic element (Background of the heart rate field) and the battery consumption was 8% - this is definitively too much. In the past I used f.example the Dosen Cycle-Datafield with dynamic Background of Heart Rate Field and I had no such Problems.

    Tomorow I want to test the battery consumption with Datafield without dynamic coloring to verify my hypothesis.

  • Did you use the latest version? 

  • Hi. I didn't have the Name of destination in my layout when I tested it, I'll get it added later. In the meantime here is a link to my XML file layout_Edge1030

    I don't know if it's related but I did notice that where other data values display $V in the Text field of the designer for display of the value, which can be edited to adjust the layout, the Text field for Name of next point & Name of destination display Eribor & Mordor respectively, which cannot be edited and also appear in the config string

    In order to test I did try editing the XML to change the Text for Name of next point to $V but when it's imported to the designer the text field still displays Eribor, which is still gets exported to the config string. I looked at the config string in a text editor to see if I could edit the string so that I could replace Eribor with $V but couldn't quite work out the syntax of each data value in each string so thought I'd better leave it to the expert.

    One observation with the $h:$m:$s time format from my ride today was that when the timer transitions into the next time period the format looks a bit unusual. ie from 59 seconds to 1 minute you get 0:0 then 0:1, 0:2 etc . More obvious is from 59:59 to 1 hour, where you get 1:0:0 then 1:0:1, 1:0:2  etc...

    A suggestion from me would be that when a time period transition is made the subordinate periods should then default to a two digit layout ie instead of 0:0, 0:1 it would be 0:00, 0:01 etc & 1:0:0, 1:0:1 would be 1:00:00, 1:00:01 etc. Maybe other users could offer their input on the validity of this suggestion

  • Hi, 

    if i am using more than ohne Dynamic Color Field i always get an IQ Error on my edge 820.