Walker

개발자 회신
2020년 7월 9일 (목), wwarby

Huh. It's not doing that for me. I did have a bug at one point where it was doing that, but I'm not sure if I ever released a version containing that bug - could you do me a favour and double check that you're running version 1.0.5? (and importantly, that the walk you're looking at was recorded with version 1.0.5). Maybe try uninstalling and reinstalling Walker if you're not sure - I don't think it's actually possible to see the version on the watch itself. I have one trick up my sleeve I could use that might solve this problem if it still exists because I don't have an explicit translation to English as it's the "default" language - I could add an English translation file but I'm not sure why that would be necessary for your watch and not mine unless maybe it was purchased in Spain and somehow for you Spanish is the "default" language or something like that?

개발자 회신
2020년 7월 9일 (목), wwarby

It doesn't really fit with my intentions for this DataField I'm afraid. I want to keep the design of Walker quite clean and focused on casual walking scenarios. The design is quite dense already and I don't want to stuff every millimetre of negative space with data. Also (to me at least), altitude is of interest when you're "hiking", and if I were to add it I could easily see myself drifting towards trying to shoehorn in data for total ascent, cadence, bearing direction and other things that hikers care about and people out for a casual afternoon stroll just don't. I might make a "Hiker" companion DataField with that kind of stuff in at some point (no promises) but it's not something I want to see in Walker at the moment I'm afraid. On a side note I'm so close to the 16K memory limit of the older watches (that includes the FR3 I think) that I can't add so much as a setting for background colour at the moment without crashing the device, so I'd have to find some memory savings somewhere before I can add anything for older watched anyway.

개발자 회신
2020년 7월 8일 (수), wwarby

Hi Ray, I've had a few issues with this so I wouldn't rule out the possibility there's still a bug in there somewhere, but the settings for this are a bit confusing. In the Garmin Connect app there is only one setting for "Units" which gets synced to the the watch, but in the activity settings on the watch there are actually separate settings for "Pace Units" and "Distance Units". In a previous version I wasn't respecting the difference between those settings and it was causing unexpected behaviour for another user - can you check whether you have both settings set to MPH?

개발자 회신
2020년 7월 7일 (화), wwarby

It's strange - the device simulator for Garmin's SDK lets me switch your watch model's background colour, so I'm surprised they would simulate a setting that's not actually available on the device. In any case I tried adding a setting for it this morning (which is easy enough to do), but it's pushing me over the memory limit of your device and crashing the simulator. You may not be aware, but the FR 735 limits DataFields to 16KB of memory, of which about 9KB is taken up just by the DataField itself before you even get started. Staying under this limit is INCREDIBLY hard (I had to draw that heart icon with two circles and an upside down triangle instead of using an image file just to save 200 bytes for example). The problem is, I've picked off all the low hanging fruit on memory consumption and I'm still hovering around 15.9KB used, so adding literally anything at this point is going to mean taking something else away. I'll get my thinking cap on and see if I can find the extra 50 bytes or so of memory needed to add the feature, but can't promise anything :)

개발자 회신
2020년 7월 7일 (화), wwarby

Urgh. I knew I'd accidentally do that at some point. I have a bit of code in the project that I uncomment to take screenshots, and I accidentally left it in the build. It forces the values to the ones you see in the screenshots. Apologies, one star review well and truly deserved in this case. I've just uploaded version 1.0.4 which corrects the problem. I'll work out some kind of process that prevents me from doing that again - apologies for any inconvenience.

개발자 회신
2020년 7월 7일 (화), wwarby

You're welcome ;) I had the same need - couldn't find what I was looking for in the Connect IQ store, so I built it myself.

개발자 회신
2020년 7월 6일 (월), wwarby

Hi Palle, the background colour is in the settings of the Walk activity itself on the watch, not in the settings for the data field on the phone app. The setting is called Background Color, the relevant page on the manual for my fenix 5x watch is here: https://www8.garmin.com/manuals/webhelp/fenix5/EN-US/GUID-E03FFCFD-15AD-401E-A15D-715629C6DBF0.html. I believe on older watches like the Forerunner 235 the setting is in a different place because it's for the whole watch rather than one specific activity, but all watches have the setting. Hope that helps :)

개발자 회신
2020년 7월 6일 (월), wwarby

Thanks for the feedback Carmen. After a bit of experimentation I found I was able to increase the font size a bit for your device and still make everything fit on screen. I've released an update (version 1.0.3) that increases the size of all the text in the layout for the Forerunner 230, 235, 630 and 735xt.

개발자 회신
2020년 7월 6일 (월), wwarby

Bad translation from Google: Looks nice but unfortunately I can't get it on my watch. Vivoactive 3 is among them. Response: I'm not sure why you're unable to get this data field on your vivoactive 3 as I do support that model and it works fine in the device simulator from the Garmin SDK for the vivoactive 3. I'd suggest you get in touch with Garmin as it's more likely a user support issue than a technical problem with the design of Walker itself.

개발자 회신
2020년 6월 30일 (화), wwarby

Translation: Why can't I update the data field? It is not installed with every new version. I have to uninstall and reinstall it every time. Got the Venu Reply: I'm afraid this is entirely outside my control as a developer - once I upload a new version it is Garmin's responsibility to get it onto user devices. I've experienced this exact problem myself and can only think that it comes down to just waiting patiently :) I expect Garmin would update your watch automatically after a few hours and I have heard from other users that it is updating just fine, but as I always want to test my latest version immediately after upload I invariably have to delete and reinstall it. Apologies for the inconvenience, if there was anything I could do to make it update faster I would, but I'm afraid it's out of my hands.

개발자 회신
2020년 6월 27일 (토), wwarby

Thanks for the feedback :) That sounds like a reasonable request - I'll give some thought as to how best to present the information but in principle I see no reason not to add HR Zones.