A set of constants for the system button styles that can be used for the button style property.
This class has been removed since 7.0.0
Use <Titanium.UI.iOS.SystemButtonStyle> instead.
These constants represent standard iOS system button styles that affect the Button, ButtonBar, and TabbedBar UI elements.
The different styles are used in different places. For normal buttons which are not contained in a nav bar, toolbar, button bar or tabbed bar, the following styles apply:
BORDERED. Simple button style with a rounded border and a white background.
The default style for normal buttons.DONE. Like the bordered button, but with a blue background. Button style for a button
that indicates completion, such as OK, Save, or Go. PLAIN Button style for an undecorated button. Note that if you specify the PLAIN style, you must style the button using the other button
properties. For example, there is no indication that the button has been pressed unless you set
other properties for the selected state, such as backgroundSelectedImage and selectedColor.
When you add a button to a Toolbar, the styles have a slightly different effect:
PLAIN Button style for an undecorated button with large text and a glow effect when the
button is pressed. Default style for buttons in toolbars.BORDERED. Simple button style with a rounded border and a light blue background. DONE. Like the bordered button, but with a dark blue background. For TabbedBar and ButtonBar controls, styles have the following meaning:
PLAIN. Default style for ButtonBar and TabbedBar.BORDERED. Creates a bar like the PLAIN bar, but with a heavier border.BAR. Used on ButtonBar and TabbedBar controls to produce a more compact bar with
translucent buttons that allow the bar's background color to show through.Used with ButtonBar or TabbedBar only, to use the more condensed style used in nav bars and tool bars.
Used with ButtonBar or TabbedBar only, to use the more condensed style used in nav bars and tool bars.
This property has been removed since 3.6.0
To use a background color or gradient on a ButtonBar or TabbedBar control, you must use
the BAR style. This style creates translucent buttons that allow the bar's background
color to show through.
The style for a Done button--for example, a button that completes some task and returns to the previous view.
The style for a Done button--for example, a button that completes some task and returns to the previous view.
Used in toolbars and navigation bars.
Specifies a borderless button, the default style for toolbars, button bars, and tabbed bars.
Specifies a borderless button, the default style for toolbars, button bars, and tabbed bars.
In toolbars, this specifies an undecorated button with large text. A glow effect is used when tapped.
In button bars and tabbed bars, specifies a button with large text that is highlighted when tapped.
When used on a normal button (that is, outside of a navigation bar, toolbar, button bar or
tabbed bar), PLAIN specifies a button with no built-in decoration except its title text.
This is the style you should choose if you want to supply your own background images,
background gradient, and so on.
Note that for tabbed bar or button bars, the BAR style is used to allow the bar's background color or gradient to show through.
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
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.
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 lifecycleContainer property.
New value for the property.