| InstallerContactSite Map |
Advanced Installer User Guide | |||
The Edit Control Events Dialog page |
|
NameSelect the desired control event from the list.
ArgumentsSpecify an argument for the condition. For some events there is a list of arguments from which you can choose, for others this field is of Formatted Type. Use the button to display the Edit Formatted Type Dialog that will allow you to insert a reference to a property. Also some events may not need arguments. ConditionSpecify an execution condition for the control event. Use the to show the Edit Condition Dialog dialog which will allow you to edit a condition. The control events created in Advanced Installer can use these predefined conditions:
Examples of commonly used control conditions: A NewDialog control events is used to close one modal dialog box and open another. When a control that publishes this event is triggered, the Installer closes the current dialog and puts up a new one in its place. In the User Interface of your Installer, the Back and Next buttons will publish NewDialog events to enable navigation between the various installation dialogs. The SpawnDialog event also opens a new modal dialog box. The difference between the "NewDialog" and "SpawnDialog" events is that the latter does not destroy the current dialog. The SpawnWaitDialog event also opens a new modal dialog without closing the current one. This control event requires a condition in order to run correctly. The specified dialog is shown as long as the condition evaluates to True and is destroyed as soon as it evaluates to False. For example, you might use this control event to display a “Please Wait” dialog while the Installer computes component costs before displaying a dialog box with a SelectionTree control. The "Published Events" tab in the "Dialogs" page of an Enterprise project allows you to specify the Control Events started when a user interacts with a PushButton Control, CheckBox Control, or SelectionTree Control. These are the only controls which can initiate published control events. Each control can publish multiple control events. The installer starts each event in the order specified in the project. For example, a push button control can publish events to initiate a transition to another dialog box, exit the dialog box sequence, and begin file installation. The exception is that each control can publish at most one "NewDialog" or one "SpawnDialog" event. If multiple "NewDialog" and "SpawnDialog" control events are selected for the same control, only the last one gets published when the control is activated. |

This dialog allows you to edit a control event. A control
event is an action that is triggered when the user interacts with the
control.