List of local actions (GDC only)

Important: This feature is deprecated, its use is discouraged although not prohibited.

List of local actions

Important: Local actions are a deprecated feature. Local actions are only supported by the GDC front-end for backward compatibility. Avoid binding action views with the action names listed in the following table, and avoid changing the action defaults attributes (such as accelerators) for these actions.
Table 1. Local actions (handled by the front-end)
Local Action Name Description ON ACTION block is required Context
editcopy Copies the current selected text to the clipboard can overwrite (4)
editcut Copies the current selected text to the clipboard and removes the text from the current input widget can overwrite (4)
editpaste Pastes the clipboard content to the current input widget can overwrite (4)
nextfield Moves to the next field in the form can overwrite (1)
prevfield Moves to the previous field in the form can overwrite (1)
nextrow Moves to the next row in the list can overwrite (2)
prevrow Moves to the previous row in the list can overwrite (2)
firstrow Moves to the first row in the list can overwrite (2)
lastrow Moves to the last row in the list can overwrite (2)
nextpage Moves to the next page in the list can overwrite (2)
prevpage Moves to the previous page in the list can overwrite (2)
nexttab Moves to the next page in the folder can overwrite (3)
prevtab Moves to the previous page in the folder can overwrite (3)

Context descriptions

  1. CONSTRUCT, INPUT and INPUT ARRAY.
  2. INPUT ARRAY and DISPLAY ARRAY.
  3. Possible in any kind of interactive instruction (MENU included).
  4. DIALOG, CONSTRUCT, INPUT, PROMPT, INPUT ARRAY and DISPLAY ARRAY.

Automatic and local actions using the same name

Some predefined actions exist as both automatic actions and as local actions (like editcopy). The automatic actions are created from the dialog context. If an automatic action has to be defined and if a local action exists with the same name, the automatic action takes precedence over the local action.

For example, if the dialog context requires an editcopy runtime action, the local editcopy action will not be handled by the front-end. Identical action names are used for automatic and local action to bind with the same action view. For example, the same toolbar button created with the editcopy name will trigger the automatic action or the local action, depending on the context.