Thanks, Werner, but following your advice (ie on the dot in the case of Dist.to.Dest) I mostly (in some 95% of the attempts) land on the aforementioned Hazard/Home/Bell screen. A rather sensitive affair, at least in the case of the Edge 1050.
Thanks, Werner, but following your advice (ie on the dot in the case of Dist.to.Dest) I mostly (in some 95% of the attempts) land on the aforementioned Hazard/Home/Bell screen. A rather sensitive affair, at least in the case of the Edge 1050.
I test all the behaviours on the simulator but for UI look & feel I have to do final test on the Edge.
Unfortunately it is not 100% accurate (at least on my Edge 840).
For example bitmaps are displayed better on the real device.
import Toybox.Lang;
import Toybox.Position;
function onPosition(info as Position.Info) as Void {
// log("onPosition");
}
function initLocationEvents1(config as Number) as Void {
Position.enableLocationEvents(Position.LOCATION_CONTINUOUS…import Toybox.Lang;
import Toybox.Position;
function onPosition(info as Position.Info) as Void {
// log("onPosition");
}
function initLocationEvents1(config as Number) as Void {
Position.enableLocationEvents(Position.LOCATION_CONTINUOUS…The streak count IS stored on at least some watches - the popup when you meet your goal tells you the number
It would be great if the SDK would expose this - even if only on current/future watches
I wrote a watch face a few years ago that the Streak number…
It would be great to have at least exact install numbers par month (ideally by user and excluding reinstall), this kind of basic analytics is provided on Android and iOS stores.
As a developer I want to know how much my app is downloaded.
OK, so maybe there isn't some nice solution, like tint in the drawables.xml... But is there a at least way I can know which device's Menu2, IconMenuItem is black-on-white an which is white-on-black? I looked in simulator.json, but couldn't find it.…
OK, so it works on the watch, so I guess it is the same bug you linked to, the one that Garmin does not care about.
It is the third headache-causing and time-consuming Garmin bug that I encountered during the implementation of my relatively simple app…
Thanks for clearing things up, Jim.
Due to your information I reworte the background process. To summarize: The background process doesn't run during charging at the PC. This means, I have to check in the background process that battery level is increasing…
I think you mean the API level or "Connect IQ version", not SDK version. (Yes, the SDK version is correlated with the API version - or at least it was in the past.)
Anyway, I think you can use DeviceSettings.monkeyVersion to do what you want…
