Modules | |
Private | |
Typedefs | |
typedef void(* | AlpAttnAlertCB )(const char *sourceAppId, const char *alertTypeName, const char *handle, int argc, char *argv[], void *user_data) |
Prototype for the Attention Manager callback function. | |
typedef AlpLuid | AlpAttnId |
type of an attn alert ID | |
typedef void * | AlpAttnAlertH |
opaque type holding an alert object | |
typedef void * | AlpAttnPropertyH |
opaque type holding a property object | |
Functions | |
alp_status_t | alp_attn_alert_post (const char *sourceAppId, const char *alertTypeName, const char *handle, const char *interface, int32_t priority, int32_t duration, uint32_t nprops, AlpAttnProp *properties[]) |
Post an attention alert. | |
alp_status_t | alp_attn_alert_post_with_callback (const char *sourceAppId, const char *alertTypeName, const char *handle, const char *interface, int32_t priority, int32_t duration, uint32_t nprops, AlpAttnProp *properties[], AlpAttnAlertCB callback, void *user_data) |
Post an attention alert with a callback. | |
alp_status_t | alp_attn_alert_update (const char *sourceAppId, const char *alertTypeName, const char *handle, uint32_t nprops, AlpAttnProp *properties[]) |
Update the properties of a previously posted alert specified by the alert identifier. | |
alp_status_t | alp_attn_alert_delete (const char *sourceAppId, const char *alertTypeName, const char *handle) |
Delete a posted attention alert using the alert identifier. |
|
Prototype for the Attention Manager callback function.
|
|
opaque type holding an alert object
|
|
type of an attn alert ID
|
|
opaque type holding a property object
|
|
Delete a posted attention alert using the alert identifier.
|
|
Post an attention alert. Post an alert to the attention manager. This version is primarily meant to be used by applications. Applications received notification of a user action taken by being launched (or relaunched) via the application manager with the arguments specified for that particular user action. This is done because there is no guarantee that the desired application will be running when the alert dialog or the alert list is displayed and the user selects an action for the alert. The properties provided in the post and update calls control how and what is displayed in the alert dialog and the alert list. They also specify the actions to be associated with the buttons present in the user interface. What determines whether a posted alert will cause an alert dialog to be displayed or simply have the alert show up on the alert list depends on the supplied priority and a predefined ruleset which specifies how alerts are to be handled. The default handling of priority 1 and 2 is to present a system dialog on the screen which will require user response. Priority 3 will accept the posted alert for display in the alert list and play an attention alert sound (or vibrate depending on the quite mode). Priority 4 will only play the sound.
|
|
Post an attention alert with a callback. Post an alert to the attention manager. This version is primarily meant to be used by a service daemon that can't be launched like an application and must rely on a callback to receive notification of a user action taken during the display of the alert by the attention alert user interface. Depending on the configuration of the actions given for this alert (either through explicit properties or specified in the alert interface specification), one or more of the user actions may result in the callback being called with the supplied user_data and list of arguments configured for the given action taken. The properties provided in the post and update calls control how and what is displayed in the alert dialog and the alert list. They also specify the actions to be associated with the buttons present in the user interface. What determines whether a posted alert will cause an alert dialog to be displayed or simply have the alert show up on the alert list depends on the supplied priority and a predefined ruleset which specifies how alerts are to be handled. The default handling of priority 1 and 2 is to present a system dialog on the screen which will require user response. Priority 3 will accept the posted alert for display in the alert list and play an attention alert sound (or vibrate depending on the quite mode). Priority 4 will only play the sound.
|
|
Update the properties of a previously posted alert specified by the alert identifier. New properties will be added to the attention alert, existing properties will have their values replaced with the new values.
|