| User interface programming / Dialog actions | |
A default action view is created to render an action handler when no explicit action view exists for it.
If no explicit action view is defined, such as a toolbar button, a topmenu item or a simple button in the form layout, the front end creates a default action view for each COMMAND or ON ACTION action handler, or implicit action such as insert/delete in INPUT ARRAY, in the current interactive instruction.
The rendering of default action views depends from the platform. On a desktop front-end, the default action views appear as buttons in the action frame in the right-hand side of the current window. On a mobile device, the default action views will follow the mobile user interface standards, which can be vendor specific. For more details about default action views on mobile, see Rendering default action views on mobile.
When creating action handlers with ON KEY (or COMMAND KEY without a command name in a MENU), the default action view is invisible. If you define a text attribute in the action defaults, the default action view is made visible.
Control the default action view visibility by using the DEFAULTVIEW action attribute.
If one or more action views are defined explicitly for a given action, the front end considers that the default view is not needed. Typically, if you define in the form a BUTTONEDIT field, a BUTTON, or a TOOLBAR item that triggers the action, you do not need an additional button in the action frame.
The presentation of the default action views can be controlled with presentations style attributes for the Window AUI tree nodes.