• Replies 2194 replies
  • Subscribers 80 subscribers
  • Views 344970 views
  • Users 0 members are here
Options
Related

HMs DIY #1-6

hundsmiachn
over 5 years ago

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

 

  • over 5 years ago in reply to Frun37

    Hi

    As I posted, I had no time to match the fonts for all devices. You will have to adjust the fonts.txt file so it matches best your watch.

    Here are two xml files with all the fonts available. You will have to adjust the font type, size, and the 3 x-offsets for every alignment and the y offset. A short description is in the fonts.txt file.

    font_test1.xml

    font_test2.xml

    Just load the first xml file, copy the string to the settings of your watch and then compare your watch with the designer and adjust the fonts.txt file.

    If you change fonts.txt you will have to restart the designer!

    Because there are over a thousand font combinations for all devices it will just take time to adjust them all...

    regards

    Erich

  • over 5 years ago

    Hi,

    thanks a lot for adding of current lap pace. 

    I have a further question. On the FR the place is limited. Therefore I want only show the pace up to 9:59min/km or similar to save space. Is this possible? In the old DIY I used a white rectangle over the first number (if bigger than 10min/km). But in your app that doesn't work.

    Maybe there is another solution.

    Thanks

    Christian

  • over 5 years ago in reply to Christian888

    Hi

    At the moment, all graphics are drawn first and over them are the texts drawn, so your solution is not possible.

    I wanted to limit the pace over 10 anyway, because it is not really precise over that value.

    Will add that check in the next release.

    regards

    Erich

  • over 5 years ago in reply to hundsmiachn

    Sounds good, then I'm waiting for the next release.

    Christian 

  • over 5 years ago in reply to mcinner1

    New version 1.2.2 is out!

  • over 5 years ago in reply to hundsmiachn

    And once again - thank you very much for your work!

    A question on the side:
    With version 1.1.2 we got the possibility to define several strings. But if I want to use several DIY data fields in one activity profile, I think that doesn't help? So it would need clones of the app - right?
    From the name "DIY #1" I guess that this is planned after reaching a „end development level“?

  • over 5 years ago in reply to mcinner1

    Thanks for the tip. I'll give it a tryThumbsup

  • over 5 years ago in reply to hundsmiachn

    Enjoying trying out the new features.

    On my training ride tonight I noticed some differences with the Lap Time/Lap Number information in the app compared to the native Garmin datafields & thought I'd ask if this was intentional

    In the Garmin datafields the Lap Number begins at 0 when the start button is pressed & the Lap Time starts to count up. The Lap Number only increments & Lap Time reset when either the Lap Button is pressed or if in an interval workout; on completion of each interval. Stopping & Starting the timer has no effect on either the Lap Number or Lap Time other than pausing it while the timer is stopped.

    In the DIY datafield the Lap Number is initially 0, however when the start button is pressed the Lap Number increments & the Lap Time starts to count up. The Lap Number then increments & Lap Time reset only when the Lap Button is pressed it doesn't increment if in an interval workout when each interval is completed. Stopping & Starting the timer also causes the Lap Number increment & resets the Lap Time.

    I was thinking that maybe these differences are due to restrictions imposed by the functions made available to CIQ developers, but thought I'd ask