Used to specify the placement of the ButtonBar on the device screen. If button-specific positional attributes (left, top, height, width) are not set, the values for all individual buttons will be calculated based on the value (if any) and Positional Attributes. If unspecified, horizontal orientation will be selected. The horizontal setting will position the bar across the screen from left to right vertical from top to bottom. Used to select the horizontal or vertical orientation of buttons on the ButtonBar. Used to specify ButtonBar transparency as a percentage from 0-100 (0=none 100=full). Note: Setting the font size for individual buttons is not supported. If left unspecified, text size will be chosen based on the device default. This size is adjusted based on the current density and user font size preference. Used to specify the default text size interpreted as 'scaled pixel' units. In such cases, Zebra recommends using the buttonImagePressed parameter.

If the WebView is resized and the ButtonBar is not rendered on top of the WebView layout, button color can sometimes render improperly.

If no color is specified, the default color is yellow.Used to specify the color of the entire ButtonBar using HTML hexadecimal color values when any button in the bar is pressed. In such cases, Zebra recommends using the buttonImage parameter. If an image is specified as a button background, barColor setting is ignored.If no color is specified, the default color is blue.Setting the color for individual buttons is not supported.Used to specify the color of the entire ButtonBar using HTML hexadecimal color values. These tags must be enclosed within the ButtonBar node for which the settings are intended. ExampleīuttonBar-specific parameters are used to specify attributes that apply to the entire ButtonBar. Note: If an attribute defined for a ButtonBar conflicts with one or more Button-specific parameters, the individual Button setting will take precedence. If multiple ButtonBars are required, they must be defined one after another within the the parent node (as explained above). Numbered ButtonBar1 through ButtonBar10, this node contains all the specific ButtonBar parameters (color, transparency, position, etc.) and attributes of a particular numbered ButtonBar, as well as the nodes. Button1 attributes, parameters, text (label) and action ButtonBar1 parameters and attributes (color, transparency, position, etc.) This is the head or parent node of the button.xml file all tags should be contained with this node as shown in the example below. User should pass valid values for all button/bar related parameters. If user sets any invalid value for button parameters, ButtonBar may not show up and the behavior is undefined. However if someone wants to set auto-rotate to on, they should ensure to create different ButtonBars for Landscape and Portrait mode and apply them accordingly through the screen orientation event. In Enterprise Browser, it is always recommended to set auto-rotate to off for Enterprise web applications. One may have to create different button.xml for different screen resolution device. The positional and size related attributes (left, top, height and width) should be defined as per target device screen resolution and current screen orientation.

The positional attributes, action, color, transparency and all other view related parameters can be fully customized by specifying those values as key value pair in this xml file. Enterprise Browser currently supports 10 ButtonBars (ButtonBar1 through ButtonBar10) and all definitions are maintained in the button.xml file. The button.xml file stores all configuration settings for custom on-screen buttons of an app. See Customize Enterprise Browser for details. ButtonBars can be shown and hidden programmatically as required by an app's pages through methods implemented in one of 10 ButtonBar APIs currently supported. Both files are stored on the device, and their paths are specified in corresponding tags in the app's Config.xml file. If one or more of the buttons is to execute JavaScript, the code is contained in a second file called CustomScript.xml. The number of buttons or keys and the appearance, layout, on-screen position, functions and all other attributes are controlled through a file called button.xml. Apps made with Enterprise Browser 1.7 (and higher) for Android can be accompanied by a series 1-10 custom on-screen buttons or keys that can perform virtually any function available to the device, including launching an app or activity, scanning a barcode, sending an intent or executing a JavaScript code snippet.

Buttonbar set button size