It seems like even though Fenix 7S passes the Toybox.Graphics has :BufferedBitmap check, calling new Graphics.BufferedBitmap(..) causes a crash
My sample code:
Starting my first app development, I am running visual studio code with the monkey C extension. I've been able to build my app (at least I end up with a prg file) for the 1030, but when I launch the simulator for the 1030 I'm a bit lost. All I see if…
If the docs are to be believed, then the at least the original Vivoactive does not have a magnetic compass. (I'm assuming that in this context, "compass" means magnetic compass and not GPS compass.)
Micro Payments must be enabled manually - by contacting paypal... And I'm not sure if a business account is necessary, but yes, I have one - but only because I do need API access and that's only available for a business account. I don't see hidden fees…
Not sure if you've left this out of the code you posted above, but I don't see a <strings> section in your properties, yet you reference at least one?
From what you've posted, it looks like you need to add:
Yes, as we wrote before, we are using Activity.getActivityInfo().ambientPressure, meanSeaLevelPressure and rawAmbientPressure, and none of them seem to match the value of the pressure at GARMIN app, or the readings other watchfaces do. They might be getting…
Interesting!! Grabbing the EDGE "device" temp is often misleading - it bakes in the exposed sun (at least here in Florida) and the temps can be 20+ degrees too high. Plus it was a pain to grab using background processing.
Apparently, CIQ 3.2…
But the right syntax is
Application.Properties etc... Right ?
It depends on the using clause. Either of these would be correct...
function f() {
var value = Toybox.Application.Properties.getValue(key);
}
or
using Toybox…
In the sim, under File, use "View Watchface Diagnostics."
You can see how you're doing.
The WF must be running in low power mode.
Here's an example (total time that second is 9.29ms):
If after a full minute, you've exceeded the avg…
Does the original image have aliasing issues like that? If so, then that is definitely a problem.
The best way to ensure you get what you want is to use the color palette available on the device when creating your assets and to not scale them after. Scaling…
