Platforms to show: All Mac Windows Linux Cross-Platform
Back to CLLocationManagerMBS class.
CLLocationManagerMBS.didChangeAuthorizationStatus(status as Integer)
Type | Topic | Plugin | Version | macOS | Windows | Linux | iOS | Targets |
event | CoreLocation | MBS MacFrameworks Plugin | 11.2 | ✅ Yes | ❌ No | ❌ No | ❌ No |
status: The new authorization status for the application.
This method is called whenever the application's ability to use location services changes. Changes can occur because the user allowed or denied the use of location services for your application or for the system as a whole.
CLLocationManagerMBS.didEnterRegion(region as CLRegionMBS)
Type | Topic | Plugin | Version | macOS | Windows | Linux | iOS | Targets |
event | CoreLocation | MBS MacFrameworks Plugin | 11.2 | ✅ Yes | ❌ No | ❌ No | ❌ No |
region: An object containing information about the region that was entered.
The region object provided may not be the same one that was registered. As a result, you should never perform pointer-level comparisons to determine equality. Instead, use the region's identifier string to determine if your delegate should respond.
CLLocationManagerMBS.didExitRegion(region as CLRegionMBS)
Type | Topic | Plugin | Version | macOS | Windows | Linux | iOS | Targets |
event | CoreLocation | MBS MacFrameworks Plugin | 11.2 | ✅ Yes | ❌ No | ❌ No | ❌ No |
manager: The location manager object reporting the event.
region: An object containing information about the region that was exited.
The region object provided may not be the same one that was registered. As a result, you should never perform pointer-level comparisons to determine equality. Instead, use the region's identifier string to determine if your delegate should respond.
CLLocationManagerMBS.didFailWithError(error as NSErrorMBS)
Type | Topic | Plugin | Version | macOS | Windows | Linux | iOS | Targets |
event | CoreLocation | MBS MacFrameworks Plugin | 11.2 | ✅ Yes | ❌ No | ❌ No | ❌ No |
error: The error object containing the reason why the location could not be retrieved.
If the location service is unable to retrieve a location fix right away, it reports a kCLErrorLocationUnknown error and keeps trying. In such a situation, you can simply ignore the error and wait for a new event.
If the user denies your application's use of the location service, this method reports a kCLErrorDenied error. Upon receiving such an error, you should stop the location service.
CLLocationManagerMBS.didFinishDeferredUpdatesWithError(error as NSErrorMBS)
Type | Topic | Plugin | Version | macOS | Windows | Linux | iOS | Targets |
event | CoreLocation | MBS MacFrameworks Plugin | 13.5 | ✅ Yes | ❌ No | ❌ No | ❌ No |
Stopping location, disallowing deferred updates, and meeting a specified criterion are all possible reasons for finishing deferred updates.
An error will be returned if deferred updates end before the specified criteria are met (see CLError).
Requires Mac OS X 10.9.
CLLocationManagerMBS.didStartMonitoringForRegion(region as CLRegionMBS)
Type | Topic | Plugin | Version | macOS | Windows | Linux | iOS | Targets |
event | CoreLocation | MBS MacFrameworks Plugin | 12.3 | ✅ Yes | ❌ No | ❌ No | ❌ No |
region: The region that is being monitored.
CLLocationManagerMBS.didUpdate(newLocation as CLLocationMBS, oldLocation as CLLocationMBS)
Type | Topic | Plugin | Version | macOS | Windows | Linux | iOS | Targets |
event | CoreLocation | MBS MacFrameworks Plugin | 11.2 | ✅ Yes | ❌ No | ❌ No | ❌ No |
newLocation: The new location data.
oldLocation: The location data from the previous update. If this is the first update event delivered by this location manager, this parameter is nil.
By the time this event is called, the new location data is also available directly from the CLLocationManagerMBS object. The newLocation parameter may contain the data that was cached from a previous usage of the location service. You can use the timestamp property of the location object to determine how recent the location data is.
CLLocationManagerMBS.didUpdateHeading(newHeading as CLHeadingMBS)
Type | Topic | Plugin | Version | macOS | Windows | Linux | iOS | Targets |
event | CoreLocation | MBS MacFrameworks Plugin | 12.3 | ✅ Yes | ❌ No | ❌ No | ❌ No |
Implementation of this method is optional but expected if you start heading updates using the startUpdatingHeading method.
The location manager object calls this method after you initially start the heading service. Subsequent events are delivered when the previously reported value changes by more than the value specified in the headingFilter property of the location manager object.
CLLocationManagerMBS.didUpdateLocations(locations() as CLLocationMBS)
Type | Topic | Plugin | Version | macOS | Windows | Linux | iOS | Targets |
event | CoreLocation | MBS MacFrameworks Plugin | 13.5 | ✅ Yes | ❌ No | ❌ No | ❌ No |
Required for delivery of deferred locations.
If implemented, updates will not be delivered to didUpdate.
Requires Mac OS X 10.9.
CLLocationManagerMBS.monitoringDidFailForRegion(region as CLRegionMBS, error as NSErrorMBS)
Type | Topic | Plugin | Version | macOS | Windows | Linux | iOS | Targets |
event | CoreLocation | MBS MacFrameworks Plugin | 11.2 | ✅ Yes | ❌ No | ❌ No | ❌ No |
region: The region for which the error occurred.
error: An error object containing the error code that indicates why region monitoring failed.
If an error occurs while trying to monitor a given region, the location manager sends this message to its delegate. Region monitoring might fail because the region itself cannot be monitored or because there was a more general failure in configuring the region monitoring service.
Although implementation of this event is optional, it is recommended that you implement it if you use region monitoring in your application.
The items on this page are in the following plugins: MBS MacFrameworks Plugin.