WatchFace crashes when my phone's bluetooth is off and while I'm sleeping

Hi there lads,

I'm testing my WatchFace very hard for several days and nights, on my own fenix6xpro watch. The performance of the watch in my eyes is excellent, but it's been two times that I've disconnected the bluetooth from my phone before going to sleep at night, and when I wake up, I see that the watch has one of the default Garmin WatchFace running.

When I go to all the WatchFaces on the watch, I see that mine has the warning triangle, and when I select apply, it doesn't work.

Once I turn the bluetooth back on on my phone, and apply my WatchFace again, then it works again.

I'm trying to reproduce the error in the simulator but I can't do it. I have try catch in my functions, and the total execution time when it's in low battery mode is about 21 seconds, I know that maybe I should lower that time more, but I think it's something else.

What could be going on here? Any suggestions?

Best regards,

/Juan

  • I did my first weather widget for CIQ back in 2015.  At that time, Toybox.Weather didn't exist so I got the data from an external website, so I've been doing this for some time! Partly sunny

  • But rounding is the wrong approach to me, even without a decimal point. if it's 109.99 display 109, as it's not 110...Maybe really close to 110, but not there yet.

    I can easily make the opposite argument. If the temperature is 0.9 C (or 32.9 F), you don’t want to display 0 C / 32 F and give the user the impression that the temperature is at the freezing point, when actually it’s nearly 1 degree higher. Hey, I wanna know if the skating rinks are frozen or not. (Yes, this is a facetious example.)

    IOW, your reasoning privileges the question “how hot is it?” over “how cold is it?”, perhaps bc you live in Arizona. For the same reason, you initially implied that converting to F is usually the right thing to do (or the “default” behavior.) It never crossed your mind that some people live in places where Celsius is the default.

    Maybe it’s because of ambiguities like this, where there’s no “right answer”, that people tend to use a “fair” rounding system when it comes to handling data that has more precision than the UI is going to display, such as round to nearest integer or even banker’s rounding.

    I can’t speak for anyone else, but out of all the possible rounding strategies, I would say truncation is the worst (all other things being equal). But again, my only point was raise awareness of the issue. It could very well be the strategy that OP wants to use.

    Even my wall clocks that show indoor temperature have 1 decimal point....

    But are they rounding to the nearest 0.1 or truncating to the nearest 0.1? Again there are two completely separate issues here which you have conflated:

    - how many decimal points to show

    - what rounding strategy to use (truncation or round to nearest)

    I will reiterate that:

    - weather.com has 0 decimal places

    - iphone shows 0 decimal places

    - Windows weather widget shows 0 decimal places

    Additionally, Garmin built-in watchfaces (at least on my 955) show the temperature as an integer (0 decimal places). The Garmin weather widget also show temperatures as integers. This makes a lot of sense for a UI with extremely limited space.

    I’ll also point out that when you talk to normal people and ask them what the temperature is, they’ll something like it’s “20 degrees” (or “68 degrees” in America), they’ll *never* say “it’s 20.9 degrees”.

    Similarly, have you ever watched a weather forecast in your life? They’ll say it’s a high of 28 and low of 19 (I don’t feel like converting to fahrenheit), and they’ll *never* say it’s a high of 28.8 and low of 19.5.

    So it’s extremely disingenuous (as usual) to say “even my wall clocks that show indoor temperature have 1 decimal point” as if they aren’t the exception to the rule, and as if indoor temperature is the same as the weather.

    Yes, my cheap indoor thermometer shows 1 decimal place for temperature, as well as my digital thermostat. That kind of makes sense for room temperature, since we typically try to control it using heat or A/C, so it makes sense to want to see granular changes. But funnily enough, my thermostat only allows the desired temperature to be set in increments of 0.5 degrees. I wouldn’t be surprised if the display of the current temperature works the same way (I’ve never seen any decimals other than .0 and .5). 

    Please show me an example of an app, website or device aimed at normal ppl which shows the weather, with more than 0 decimal places. Even if you can do that, I guarantee it’ll be vastly outnumbered by all the examples of things that show 0 places.

  • when it's 109.9 do they show 109 or 110 is the real question.

  • Here's Weather Underground:

    Notice who they are associated with:

    Let's just agree to disagree.