The Titanium binding of an Android PendingIntent.
Use the Titanium.Android.createPendingIntent method to create a pending intent.
The type of Intent you pass to createPendingIntent determines what kind of
PendingIntent is created. Each type corresponds directly with a get method on
Android's PendingIntent:
To create a PendingIntent that starts an activity, pass in an activity intent,
created with createIntent. This is equivalent to
calling the native Android PendingIntent.getActivity method. See
PendingIntent.getActivity in the Android API Reference
To create a PendingIntent that starts a service, pass in a service intent,
created with createServiceIntent. This is
equivalent to calling the native Android PendingIntent.getService method. See
PendingIntent.getService in the Android API Reference.
The PendingIntent is always associated with the activity that was the current activity
when the intent was created.
Note that this PendingIntent is designed primarily to be used with the
Notification object. It does not support all features
of the native Android PendingIntent -- in particular,
broadcast pending intents are not supported.
See also:
The name of the API that this proxy corresponds to.
The name of the API that this proxy corresponds to.
The value of this property is the fully qualified name of the API. For example, Button
returns Ti.UI.Button.
Indicates if the proxy will bubble an event to its parent.
Some proxies (most commonly views) have a relationship to other proxies, often established by the add() method. For example, for a button added to a window, a click event on the button would bubble up to the window. Other common parents are table sections to their rows, table views to their sections, and scrollable views to their views. Set this property to false to disable the bubbling to the proxy's parent.
Default: true
Flags used for creating the Pending Intent.
This API can be assigned the following constants:
The Window or TabGroup whose Activity lifecycle should be triggered on the proxy.
The Window or TabGroup whose Activity lifecycle should be triggered on the proxy.
If this property is set to a Window or TabGroup, then the corresponding Activity lifecycle event callbacks will also be called on the proxy. Proxies that require the activity lifecycle will need this property set to the appropriate containing Window or TabGroup.
If this property is true, flag Titanium.Android.FLAG_UPDATE_CURRENT will be
appended to flags automatically. Default value is true.
Adds the specified callback as an event listener for the named event.
Name of the event.
Callback function to invoke when the event is fired.
Applies the properties to the proxy.
Properties are supplied as a dictionary. Each key-value pair in the object is applied to the proxy such that myproxy[key] = value.
A dictionary of properties to apply.
Fires a synthesized event to any registered listeners.
Name of the event.
A dictionary of keys and values to add to the Titanium.Event object sent to the listeners.
Removes the specified callback as an event listener for the named event.
Multiple listeners can be registered for the same event, so the
callback parameter is used to determine which listener to remove.
When adding a listener, you must save a reference to the callback function in order to remove the listener later:
var listener = function() { Ti.API.info("Event listener called."); }
window.addEventListener('click', listener);
To remove the listener, pass in a reference to the callback function:
window.removeEventListener('click', listener);
Name of the event.
Callback function to remove. Must be the same function passed to addEventListener.
Sets the value of the bubbleParent property.
New value for the property.
Sets the value of the flags property.
New value for the property.
Sets the value of the intent property.
New value for the property.
Sets the value of the lifecycleContainer property.
New value for the property.
Sets the value of the updateCurrentIntent property.
New value for the property.