The possible invocation target types.
#include <bps/navigator_invoke.h>
typedef enum {
NAVIGATOR_INVOKE_TARGET_TYPE_UNSPECIFIED = 0x00
NAVIGATOR_INVOKE_TARGET_TYPE_APPLICATION = 0x01
NAVIGATOR_INVOKE_TARGET_TYPE_CARD = 0x02
NAVIGATOR_INVOKE_TARGET_TYPE_VIEWER = 0x04
NAVIGATOR_INVOKE_TARGET_TYPE_SERVICE = 0x08
NAVIGATOR_INVOKE_TARGET_TYPE_SELF = 0x10
NAVIGATOR_INVOKE_TARGET_TYPE_HEADLESS = 0x40
} navigator_invoke_target_type_t;
BlackBerry 10.0.0
Applications are software designed to perform specific tasks.
Cards are compact windows that allow an application to expose functionality so that it can be imported in to the flow of another application. Cards may be stacked multiple layers when one card uses another. However, each layer of the stack can stack only one child card at a time. For example, the Universal Inbox list may stack a card to preview an email message. The message card may in turn stack a card to preview an image attachment. The attachment card may then also stack a card to share the image, and so on. The peeking feature exclusive to cards allows users to "peek" back behind the current card to reveal its parent's content using a swipe gesture. Peeking is handled in the Navigator API.
Deprecated:
The use of viewers has been deprecated - use applications or cards as invocation targets instead.
Indicates that the target is a viewer. Viewers are embedded applications that can render a certain content type (images for example). They appear as part of the root application rather than as a separate application.
The meaning of a service value is reserved for future use.
This enumeration defines the possible types of targets to query for with the navigator_invoke_query_t structure. This is used by the brokering system to filter for targets that are of the given type.