The interaction model / Controlling user actions |
If no explicit action view is defined, such as a toolbar button, or a topmenu item or a simple button in the form layout, the front end creates a default action view for each MENU COMMAND or ON ACTION action handler used in the current interactive instruction. Typically, the default action views appear as buttons in the action frame in the right part of the current window.
When creating actions with ON KEY (or COMMAND KEY without a command name in a MENU), the default action view gets invisible. However, if you define a text attribute in the action defaults, the default button is made visible.
Control the default action view visibility by using the DEFAULTVIEW action default attribute or the defaultView attribute in the .4ad resource files.
If one or more action views are defined explicitly for a given action, the front end considers that the default view is no longer needed, and hides the corresponding button. 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.