Creating and Configuring Custom Dialogs
InstallShield 2020
Consider the following tips when you create and configure custom dialogs in different project types.
InstallScript and InstallScript MSI Projects
When you add a new dialog in the Dialogs view, an entry for the dialog is added to the Dialog table. You can directly modify data in this table in the Direct Editor.
In the Direct Editor, you can specify a value for the ISResourceId field for the new dialog. This ISResourceId value is used within the script to identify this dialog.
Once you have added the dialog to your project, you need to call functions such as EzDefineDialog and WaitOnDialog to load this dialog in memory and display it at run time. The corresponding ISResourceId value in the Dialog table is used as the fourth argument of EzDefineDialog to reference the custom dialog. Also, in the second argument of EzDefineDialog, it is advantageous to specify ISUSER as opposed to a null string. The EzDefineDialog function should look like the following:
EzDefineDialog("MyCustomDialog", ISUSER, "", 12005)
In the above example, 12005 is the ISResourceId of this custom dialog, as specified in the Dialog table.
Custom dialog functions can then be called to manipulate the custom dialog to your needs. These functions are documented in the InstallScript Language Reference.
Basic MSI Project
When you create a custom dialog in the Dialogs view of a Basic MSI project, a Windows Installer–type dialog is created. InstallScript custom dialog functions cannot be used with this Windows Installer–type dialog. To display this dialog in your installation, it must be placed in sequence between two dialogs by using their Next and Back controls.
See Also
Creating New Custom Dialogs in InstallScript and InstallScript MSI Projects