operand1 | ||||||
PROCESS GUI ACTION
action-name WITH
|
nX
|
[GIVING operand2]
|
||||
PARAMETERS-clause |
This document covers the following topics:
Related Statement: OPEN
DIALOG
| CLOSE
DIALOG
| SEND
EVENT
Belongs to Function Group: Event-Driven Programming
The PROCESS GUI
statement is used to perform an action.
An action in this context is a procedure frequently needed in event-driven
applications.
Operand Definition Table:
Operand | Possible Structure | Possible Formats | Referencing Permitted | Dynamic Definition | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
operand1*
|
C | S | A | A | U | N | P | I | F | B | D | T | L | G | yes | no | ||||
operand2
|
S | N | P | I | yes | no |
* The structure and format actually possible depend on the action to be performed.
Syntax Element Description:
Syntax Element | Description |
---|---|
action-name
|
Action to be Invoked:
As |
operand1
|
Passing Parameters to the Action:
As |
PARAMETERS
|
See Passing Parameters by Name below. |
nX
|
Parameters to be Skipped:
With the notation
A parameter that is to be skipped must be defined as "optional" in the ActiveX control's method. If a parameter is defined as "optional", this means that a value can - but need not - be passed from the invoking object to such a parameter. |
GIVING
operand2
|
Field for Response Code:
As |
For the action ADD
, you can also pass parameters
by name (instead of position); to do so, you use the
PARAMETERS-clause:
PARAMETERS
{parameter-name=operand1}
|
END-PARAMETERS
|
This clause can only be used for the action ADD
, not
for any other action.
If the action has optional parameters (that is, parameters that
need not to be specified), you can use the notation
nX
as a placeholder for
n
not specified parameters. Currently,
the only actions that can have optional parameters are the methods and the
parameterized properties of ActiveX controls.