Use the <button> <object type> to create a clickable <button>, a <tabbed button|tabbed window>, or a <menu>.

Button objects can be push buttons, checkboxes, radio buttons, or menus, depending on the setting of their style <property>.

A button whose style is set to "menu" can be a <popup> or <contextual menu>, pulldown menu, option menu, <tabbed button>, or <combo box>, depending on the setting of its <menuMode> <property>.

A button is contained in a card, group, or background. Buttons cannot contain other objects.

The button object has a number of properties and messages associated with it. To see a list of messages that can be sent to a button as a result of user actions or internal LiveCode events, open the "LiveCode Language Dictionary" page of the main Documentation window, ensure that the button column is visible and use sort and filter to bring the relevant entries to the top.

>*Note:* A standard button is rendered by the operating system, not LiveCode. Changing certain properties of such a button will cause the button to stop honouring the native theme. Properties that affect the button's colour and border may cause this issue.

References: templateButton (keyword), control (keyword), button (keyword), menu (keyword), menuMode (property), popup (command), property (glossary), tabbed button (glossary), contextual menu (glossary), object type (glossary), combo box (glossary)

Use the <card> <object type> to display different sets of <control|controls> in the same <stack window>.

A card corresponds to a single page of a stack: one card of each stack can be seen at a time. Each stack contains one or more cards.

The card object has a number of properties and messages associated with it. To see a list of messages that can be sent to a card as a result of user actions or internal LiveCode events, open the "LiveCode Language Dictionary" page of the main Documentation window, and choose "Card Messages" from the Show menu at the top. To see a list of all the properties a card can have, choose "Card Properties" from the Show menu.

References: templateCard (keyword), stack window (glossary), object type (glossary), stack (object), control (object)

Use the <field> <object type> to hold text or to provide a place for the user to enter text.

Fields can contain styled text (with different fonts, sizes, styles, and colors for different parts of the text they contain). A field can be displayed with or without horizontal and vertical scrollbars, and can be unlocked (allowing the user to enter text) or locked.

A field is contained in a card, group, or background. Fields cannot contain other objects.

The field object has a number of properties and messages associated with it. To see a list of messages that can be sent to a field as a result of user actions or internal LiveCode events, open the "LiveCode Language Dictionary" page of the main Documentation window, ensure that the field column is visible and use sort and filter to bring the relevant entries to the top

References: templateField (keyword), control (keyword), object type (glossary)

Use the <graphic> <object type> to create a geometric shape, a straight or broken line, an arrow, or other shape.

Graphics can be circles, ovals, arcs, squares, rectangles, regular polygons with any number of sides, irregular polygons (closed or open), lines (jagged or straight), or curves (smooth or broken). You specify a graphic's basic shape by setting its style <property>, and details of different basic shapes with the <points>, <arcAngle>, <startAngle>, <angle>, and <polySides> <properties>.

Unlike an image, a graphic can be resized without losing detail or becoming "jagged".

A graphic is contained in a card, group, or background. Graphics cannot contain other objects.

The graphic object has a number of properties and messages associated with it. To see a list of messages that can be sent to a graphic as a result of user actions or internal LiveCode events, open the "Dictionary" page of the main Documentation window, ensure that the graphic column is visible and use sort and filter to bring the relevant entries to the top

References: startAngle (property), angle (property), editMode (property), points (property), arcAngle (property), properties (property), polySides (property), control (keyword), image (object), property (glossary), object type (glossary)

Use the <group> <object type> to hold sets of <control|controls>, <radio button|radio-button clusters>, <menu bar|menu bars>, and <control|controls> to be displayed on more than one <card>.

A group is a set of controls that has been made into a single control. You can select, move, resize, or copy the group, and all the controls in it come with the group. You can show a border around the group (using its border <property>), a label (using the <showName> <property>), or <scrollbar|scrollbars>.

When referring to a group using the synonyms background, bkgnd, or bg, the reference is to one among the groups in a stack, rather than to one among the groups on a card. For example, the object reference background 1 indicates the first group in the current stack, not the lowest-layered group on the current card.

The group object has a number of properties and messages associated with it. To see a list of messages that can be sent to a group as a result of user actions or internal LiveCode events, open the "LiveCode Language Dictionary" page of the main Documentation window, ensure that the group column is visible and use sort and filter to bring the relevant entries to the top

References: card (keyword), control (keyword), templateGroup (keyword), showName (property), scrollbar (object), control (object), property (glossary), radio button (glossary), menu bar (glossary), object type (glossary)

Use the <image> <object type> to hold photographs, icons, and decorative elements, and to allow the user to paint.

Each image contains a bitmapped picture, which can either be imported with the import <command> or created using the <paint tool|paint tools>. An <image(keyword)> can display either its own data, or a <file> specified by the <image(object)|image's> <filename> <property>.

An image is contained in a card, group, or background. Images cannot contain other objects.

The image object has a number of properties and messages associated with it. To see a list of messages that can be sent to an image as a result of user actions or internal LiveCode events, open the "LiveCode Language Dictionary" page of the main Documentation window, ensure that the image column is visible and use sort and filter to bring the relevant entries to the top

References: filename (property), imageData (property), resizeQuality (property), templateImage (keyword), file (keyword), image (keyword), control (keyword), image (object), graphic (object), property (glossary), paint tool (glossary), bitmap (glossary), command (glossary), object type (glossary)

Use the <player> <object type> to display a movie or sound from a separate <file>.

Unlike an audio clip or video clip, a player does not contain the movie or sound data. Instead, you use the player's filename <property> to indicate the separate <file> that holds the movie or sound. This reduces the memory required by your <stack>, because the movie or sound data is only <loaded into memory> when it's being used, rather than being <loaded into memory> whenever the <stack file> is open. However, it also makes it possible for the movie or sound data to be misplaced during distribution, since the <file> is separate from your <stack file>.

A player is contained in a card, group, or background. Players cannot contain other objects.

The player object has a number of properties and messages associated with it. To see a list of messages that can be sent to a player as a result of user actions or internal LiveCode events, open the "LiveCode Language Dictionary" page of the main Documentation window, ensure that the player column is visible and use sort and filter to bring the relevant entries to the top.

>*Important:* Setting a <player|player's> filename does not automatically update its <currentTime> <property>. If you play a <movie|movie file>, then change the <player|player's> <filename> in order to play another, you must reset the <currentTime> to zero in order to start from the beginning of the second <movie> :

set the filename of player "My Player" to "SecondMovie.mov"

set the currentTime of player "My Player" to zero

References: templatePlayer (keyword), control (keyword), file (keyword), filename (property), currentTime (property), qtIdleRate (property), stack (object), player (object), property (glossary), stack file (glossary), movie (glossary), loaded into memory (glossary), object type (glossary), movie (function)

Use the <scrollbar> <object type> to display the current level or the progress of a task, or to let the user set a level or amount.

A scrollbar can be displayed as a standard scroll bar, a progress bar, or a sliding control, depending on the setting of the scrollbar's style <property>. <scrollbar|Scrollbars> can be vertical or horizontal, depending on whether their <height> or <width> is greater.

A scrollbar is contained in a card, group, or background. Scrollbars cannot contain other objects.

The scrollbar object has a number of properties and messages associated with it. To see a list of messages that can be sent to a scrollbar as a result of user actions or internal LiveCode events, open the "LiveCode Language Dictionary" page of the main Documentation window, ensure that the scrollbar column is visible and use sort and filter to bring the relevant entries to the top

References: templateScrollbar (keyword), control (keyword), height (property), width (property), scrollbarDrag (message), scrollbar (object), property (glossary), object type (glossary)