Customizing Toolbars

ArcPad Application Builder supports customization for these categories of toolbars:

• Built-in toolbars
• Custom toolbars consisting of built-in commands, user-defined commands
• Custom toolbars with user-defined commands

All toolbar customization is done in ArcPad Studio. You can create custom toolbars that work only within a specific applet or that are always loaded when ArcPad starts up.

These new toolbars can contain a combination of commands found on ArcPad software's built-in toolbars and user-defined commands that call custom scripts. You can hide or display any of ArcPad software's built-in toolbars.

Built-In Toolbars

ArcPad contains three built-in toolbars:

• Main
• Browse
• Edit/Drawing

Customization of the built-in toolbars is limited to setting their default visibility. You can replace the built-in toolbars with custom toolbars that contain built-in commands.

For example, the Main toolbar may contain more commands than you need in your application. You can create a custom toolbar that contains a subset of the Main toolbar's commands, then display this toolbar instead of the Main toolbar when ArcPad starts up.

Custom Toolbars Consisting of Only Built-In Commands

ArcPad software's built-in toolbars present a rich set of commands organized by functionality into the Main, Browse, and Edit/Drawing toolbars. However, your application may only require a subset of these commands, which you may want to present in a different arrangement.

This can easily be accomplished by creating one or more custom toolbars and adding the required built-in commands in the desired order. The visibility of the three built-in toolbars can be turned off and the custom toolbars displayed instead.

Custom Toolbars With User-Defined Commands

In some cases, ArcPad software's built-in commands may not provide the functionality you need, or you may want to automate tasks and group several actions into one command.

Advanced toolbar commands are created by writing VBScripts and linking them to the events of user-defined commands (for example, the OnClick event). When the user interacts with a user-defined command, the associated scripts are executed.