if (settings has :phoneConnected && settings.phoneConnected) {
// whatever
}
"doesn't exist" is a non sequester, as it DOES exist in the SDK documentation!
using Toybox.Application as App;
using Toybox.System as Sys;
using Toybox.WatchUi as Ui;
class C
{
var i;
}
class TestApp extends App.AppBase {
function initialize() {
var c = new C();
if (c.does_not_exist) {
Sys.println("whoa!");
}
}
}
HAS seems to be an expensive operation
... should only be needed for methods that are DOCUMENTED as only existing on some devices.
Maybe if the SDK documentation had notes about which methods are available where and when, "HAS" has a place!.
The has operator lets you check if a given object has a symbol, which could be a public method, instance variable, or even a class definition or module. The second argument is the symbol you want to check. It is handy for checking for supported APIs.
Again, there is NO reason why calling phoneConnected on a 2.40 vivoactive should crash the watch. I mean CRASH! Garmin logo and rull restart, etc. If the method that passed the compiler doesn't exist in the VM, return null, false, or something!
Because Monkey C uses dynamic typing, there are many errors for which the compiler cannot check. If the error is of high enough severity, it will raise an fatal API error and cause your app to terminate at runtime. These errors cannot be caught. At this time all of these errors are fatal and there is no way to trap them, though this may be addressed in future updates.
* Symbol Not Found: A name is being referenced that does not exist in specified object or module.
if( Toybox has :ActivityRecording ) ... seems to work on simulator, but when installed on watch, just says "This product doesn't have FIT support".
The application should NOT load on a device that does not have the methods required. (see Google Play)
However, if your app's primary functionality does not require a device feature, you should set the required attribute to "false" and check for the device feature at runtime. If the app feature is not available on the current device, gracefully degrade the corresponding app feature. For example, you can query whether a feature is available by calling hasSystemFeature() like this:PackageManager pm = getPackageManager();
if (!pm.hasSystemFeature(PackageManager.FEATURE_SENSOR_COMPASS)) {
// This device does not have a compass, turn off the compass feature
disableCompassFeature();
}
For information about all the filters you can use to control the availability of your app to users through Google Play Store, see the Filters on Google Play document.
HAS is the cheap way out, that will later need to be fixed, and no more.
There is NO excuse for ANY CIQ app to crash a device. None.. A clean compile of any CIQ app should NEVER result in the VM causing a reboot of the device.