WDWClient Class Reference
| Inherits from | NSObject |
|---|---|
| Declared in | WDWClient.h |
delegate
delegate should implement the WDWClientDelegate protocol. * All delegate methods are executed on the provided delegateQueue
@property (weak, nonatomic) id<WDWClientDelegate> delegateDeclared In
WDWClient.h
availability
Presents current state of the WDWClient
@property (assign, nonatomic, readonly) WDWClientAvailability availabilitySee Also
Declared In
WDWClient.h
delegateQueue
Dispatch queue for the WDWClientDelegate callbacks execution
@property (assign, nonatomic) dispatch_queue_t delegateQueueDiscussion
By default, all delegate messages are delivered to the main dispatch queue, which helps you to manage UI update events. You can provide your own serial queue:
self.wdwClient = dispatch_queue_create("myQueue", DISPATCH_QUEUE_SERIAL);
Declared In
WDWClient.h
– startMonitoring
Starts monitoring location and motion data. If the current location is in a relevant area, the WDW-SDK provides a json string. This string can be evaluated by the server. Also, the monitoring of the location is required for the evaluation of push message.
- (void)startMonitoringDeclared In
WDWClient.h
– stopMonitoring
Stops monitoring location and motion data. The monitoring can be restarted with startMonitoring.
- (void)stopMonitoringDeclared In
WDWClient.h
– evaluatePushMesage:
Evaluates the push notification payload. Triggers the WDWClientDelegate callback if a payload is recognized as a type of WDWWarning
- (WDWWarning *)evaluatePushMesage:(NSDictionary *)payloadParameters
payload |
you’ve received in AppDelegate’s -application:didReceiveRemoteNotification: |
|---|
Return Value
WDWWarning object if notification sourced from WDW service, nil otherwise
Discussion
Note: If your delegate implements -wdwClient:didReceiveDrivingWarning: it will be triggered on the delegateQueue as result
Declared In
WDWClient.h