The possible notification response events.


#include <bps/notification.h>
typedef enum {
      NOTIFICATION_OK = 0x00   
      NOTIFICATION_ERROR = 0x01   
} notification_response_t;


BlackBerry 10.0.0


The notification was correctly parsed.
A generic error occured in the notification.
A dialog was displayed, and the user selected an option.


libbps (For the qcc command, use the -l bps option to link against this library)


This enumeration defines the possible response events of a notification. Any notification containing a request_id member will trigger at least one response event.

If the request_id member is included in the notification, an NOTIFICATION_OK or NOTIFICATION_ERROR response event is sent immediately to indicate that a message has been correctly parsed or not, respectively. Otherwise, the response isn't sent.

If a notification_alert() call displays a dialog from which the user selects an option, a NOTIFICATION_CHOICE response event is produced. This response is sent once the user makes a selection.

All response events have a corresponding notification_response_t value associated with them. You can access them with the notification_event_get_response() function. Each response also has a Request ID which you can access with the notification_event_get_request_id() function.

You can access the button index for a NOTIFICATION_CHOICE event with the notification_event_get_choice() function. NOTIFICATION_CHOICE may also possess an item ID and/or context argument, which you can access with the notification_event_get_item_id() and notification_event_get_context() functions.

Last modified: 2014-09-30

Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus