Data field: Yet Another Runfield - YARF

Hi,

the layout of the former empty field is not final. I also did realize during my runs, that this is hard to read. This will be definitely changed in the future. Currently I optimize the performance of the datafield and also the accuracy of the paces (I probably have a good algorithm). The datafield is really at the performance limit of the 235 watch and I have to think carefully about the implementation. Probably the Forerunner 735 has more hardware resources but I need it to work better on my 235. Therefore those optimizations have the highest priority for me (I can use the algorithms than also for the interval field). The performance limit is also the reason why I have filled the empty fields with values I already have in my code.

Also I have to implement some enhancements like the stop of the lap time or the cadence supervision when the watch is stopped.

The only problem I have is time to think about things and implement it. I have a little son (3 months old) who needs also a lot of time. When the little man sleeps in the evening I can do something on the datafield :-)

Currently I clean up the code basis and rewrite some algorithms to improve performance and accuracy of the datafield. Furthermore I have to fix some bugs (e. g. fix the beep and the vibration if watch is stopped). After this I can see what I can do for you.

Sounds good. Thanks!

Hi Anton_Vaasa,

I have tried the datafield on the Fenix in the simulator. Unfortunately the Fenix's resolution is different to the Forerunner 235 which leads to distortions. I would have to adapt all the coordinates and fonts. This would be a lot of work and I want to spend time in my next project, an interval field. If you like, I would provide you with the drawing code and you can adapt it to your needs. If you send back the layout to me, I can build you a datafield dedicated to this kind of resolution.

Hi,
Thanks for the update.
What program can I edit drawing code with?
I am not a developer or very good at code... :(

Hm,

then I think it's not a good idea to send you the code. Probably adatping the code would be very time consuming for me :-( Furthermore the datafield is really at its limit regarding memory consumption. Garmin allows a datafield to consume 16 kB. The datafield has currently 15,6 kB. If I would add the adaption for the Fenix I would probably consume more than 16 kB which leads to crashes also for Forerunner users. This means, I would have to write a dedicated datafield for round watches. Maybe it's a better idea if you look for another datafield which is optimized for your watch.

You can see the problems here:


Even if I would center the datafield's coordinates somehow to the bottom, the cadence values and the heart rate values would be cut off a bit. So you have to find better font sizes and try that out. Furthermore the big pace fields are somehow too small to show the paces inside the fields. I would have to fiddle around with this size also. It would take me at least 2 hours to get that looking good.