A button consists of text or an icon (or both text and an icon) that communicates what actionoccurs when the user touches it.

Remote Programming Guide. THE SHADE STORE MOTORIZATION. BY: THE SHADE STORE. Table of Contents 1. Remote Overview 2. Initial Setup Programming 3. Sleep Mode 4. Remote & Motor Pairing. If required, to place the motor back into “Sleep Mode” press and hold the programming button for a period of 6 seconds. Most manuals provided are in the PDF file format. Adobe Reader® or equivalent PDF viewing software are required to read these manuals.

Depending on whether you want a button with text, an icon, or both, you can create thebutton in your layout in three ways:

• With text, using the Button class:
• With an icon, using the ImageButton class:
• With text and an icon, using the Button class with the android:drawableLeft attribute:

Key classes are the following:

Responding to Click Events

When the user clicks a button, the Button object receivesan on-click event.

To define the click event handler for a button, add the android:onClick attribute to the <Button> element in your XMLlayout. The value for this attribute must be the name of the method you want to call in responseto a click event. The Activity hosting the layout must then implement thecorresponding method.

For example, here's a layout with a button using android:onClick:

Within the Activity that hosts this layout, the following method handlesthe click event:

The method you declare in the android:onClick attribute must havea signature exactly as shown above. Specifically, the method must:

• Be public
• Return void
• Define a View as its only parameter (this will be the View that was clicked)

Using an OnClickListener

You can also declare the click event handler programmatically rather than in an XML layout. Thismight be necessary if you instantiate the Button at runtime or you need todeclare the click behavior in a Fragment subclass.

To declare the event handler programmatically, create an View.OnClickListener object and assign it to the button by calling setOnClickListener(View.OnClickListener). For example:

Styling Your Button

The appearance of your button (background image and font) may vary from one device toanother, because devices by different manufacturers often have different default styles forinput controls.

You can control exactly how your controls are styled using a theme that you apply to yourentire application. For instance, to ensure that all devices running Android 4.0 and higher usethe Holo theme in your app, declare android:theme='@android:style/Theme.Holo' in yourmanifest's <application> element. Also read the blog post, Holo Everywherefor information about using the Holo theme while supporting older devices.

To customize individual buttons with a different background, specify the android:background attribute with a drawable or color resource.Alternatively, you can apply a style for the button, which works in a manner similar toHTML styles to define multiple style properties such as the background, font, size, and others.For more information about applying styles, see Styles and Themes.

Borderless button

One design that can be useful is a 'borderless' button. Borderless buttons resemblebasic buttons except that they have no borders or background but still change appearance duringdifferent states, such as when clicked.

To create a borderless button, apply the borderlessButtonStylestyle to the button. For example:

Custom background

If you want to truly redefine the appearance of your button, you can specify a custombackground. Instead of supplying a simple bitmap or color, however, your background should be astate list resource that changes appearance depending on the button's current state.

You can define the state list in an XML file that defines three different images or colors to usefor the different button states.

To create a state list drawable for your button background:

1. Create three bitmaps for the button background that represent the default, pressed, andfocused button states.
   To ensure that your images fit buttons of various sizes, create the bitmaps as Nine-patch bitmaps.
2. Place the bitmaps into the res/drawable/ directory ofyour project. Be sure each bitmap is named properly to reflect the button state that they eachrepresent, such as button_default.9.png, button_pressed.9.png, and button_focused.9.png.
3. Create a new XML file in the res/drawable/ directory (name it something likebutton_custom.xml). Insert the following XML:
   This defines a single drawable resource, which will change its image based on the currentstate of the button.
   • The first <item> defines the bitmap to use when the button ispressed (activated).
   • The second <item> defines the bitmap to use when the button isfocused (when the button is highlighted using the trackball or directionalpad).
   • The third <item> defines the bitmap to use when the button is in thedefault state (it's neither pressed nor focused).
   Note: The order of the <item> elements isimportant. When this drawable is referenced, the <item> elements are traversedin-order to determine which one is appropriate for the current button state. Because the defaultbitmap is last, it is only applied when the conditions android:state_pressed andandroid:state_focused have both evaluated as false.
   This XML file now represents a singledrawable resource and when referenced by a Button for its background,the image displayed will change based on these three states.
4. Then simply apply the drawable XML file as the button background:

For more information about this XML syntax, including how to define a disabled, hovered, orother button states, read about State ListDrawable.

Additional code samples

The Android BorderlessButtons sample further demonstrates the use of the APIs covered on this page.

Buttons can be added to a Microsoft InfoPath 2010 form to enable users to click them to initiate an immediate action, such as submitting the form or querying a database. You can associate a button with rules or custom code.

In this article

About buttons

Button

Buttons are controls that you click to perform an action on the form. You can use them to perform a basic action, such as submit, refresh, or update the form, or you can use them to perform more advanced actions through rules or custom code.

Use a button when you want to:

• Submit data to one or more data sources.
• Enable users to switch to another view of the form.
• Refresh data from an external source of data.
• Clear any queried data from the form.
• Calculate data on the form.

Picture button

Picture buttons work like regular buttons, except that, instead of text on the button, indicating its function, you can use a picture. You can also set a hover picture, which causes the picture on the button to change when the user moves their mouse over the button.

Use a picture button when you want to:

• Use a picture, instead of text, to represent the action that the button performs.
• Display the image of a tab as a way of navigating between views on the form.
• Create an image map that users can click.
• Make buttons match the theme of the form and overall look and feel.

About button actions

By default, buttons have an empty Rules and Custom Code action associated with them. You will have to configure any associated rules or custom code that you want to run when you click the button. You can also configure the button to perform other actions, such as submit, refresh, or update the form. The following outlines each of the possible actions that you can select from:

• Submit This action initiates the standard submit functionality for the form, just like if the user were to click Submit on the Home tab in the filler.
• Refresh If the form is connected to one or more receive data connections, this action enables you to select one or more of those data connections to refresh the data from.
• Rules and Custom Code This is the default action for a button when it is created and runs either a rule or custom code when the button is clicked. For example, you can create a rule that switches views, closes the form, or submits the form as an email message.
• Update Form Only available for Web browser forms. The Update Form action refreshes all data in the form.
• Run Query Only available if the form is connected to a database or Web service. The Run Query action queries a database or Web service based on the values entered in the fields that are used to query the data.
• New Record Only available if the form is connected to a database or Web service. The New Record action clears the values on the form so that a user can enter new data.

Insert a button

The procedure for inserting a button is the same whether you are designing a new, blank form template or basing the design of your form template on a database or other external source of data. This is because buttons, unlike most other InfoPath controls, are not bound to fields. Instead, they are instead used to initiate an action.

1. On the form template, place the cursor where you want to insert the button.
2. On the Home tab, in the Controls group, click the type of button to insert.

Add and configure the action of a button

Do the following to change the associated action of a button: