Link to this page
Print this page
Parent topic
:
User interface programming
User interface
/
User interface programming
Dialog actions
Describes how to program action handling when the end user triggers an action on the front-end.
Action handling basics
This topic describes the basics of action views, action events and action handlers.
Defining action views in forms
How to define action views that will fire action events.
Implementing dialog action handlers
How to execute user code in ON ACTION blocks when an action is fired.
Binding action views to action handlers
How are action views of the forms bound to action handlers in the program code?
Default action views
A default action view is created to render an action handler when no explicit action view exists for it.
Configuring actions
Action attributes related to decoration, keyboard shortcuts and behavior can be defined with
action attributes
.
Data validation at action invocation
The
validate
action default attribute controls field validation when an action is fired.
Enabling and disabling actions
By default, dialog actions are enabled, however an action should be disabled when not allowed in the current context.
Hiding and showing default action views
If needed, default action views can be hidden or shown.
Sub-dialog actions in procedural DIALOG blocks
This topic describes how action are differentiated with handlers defined in a procedural DIALOG block.
Field-specific actions (INFIELD clause)
Using the
INFIELD
clause of
ON ACTION
provides automatic action activation when a field gets the focus.
Multilevel action conflicts
Action display in the contextual menu
The
CONTEXTMENU
action default attribute allows to control action visibility in the contextual menu.
Implementing the close action
The close action is a predefined action dedicated to close graphical windows (for example, with the X cross button).
Predefined actions
Genero predefines some action names for common operations of interactive instructions.
Keyboard accelerator names