I’m writing a complex datafield for navigation. When there’s a waypoint / destination active I calculate and display a few formulas and values. I’m checking if info.bearing and the other waypoint related fields are not null. I’ve noticed that the simulator struggles here, even though null it’ll still show as if the waypoint data is there (testing empty string doesn’t work either). Not a deal breaker since the wearable behaves correctly… until you stop the navigation (standard long press menu, stop navigation)… then some overflow seems to happen, bearing and distance to waypoint become gigantic numbers and those fields don’t test accurately anymore for null.
How do you test if a waypoint is active in a complex datafield? I believe I noticed the same behavior in a widget too.
Any fix to prevent the big numbers from happening? It clutters the screen and a redraw keeps those odd values displayed.