Overriding the Default Behavior of a Navigation Button on a Wizard Page
InstallShield 2022
Project:This information applies to the following project types:
| • | Advanced UI |
| • | Suite/Advanced UI |
Edition:The Advanced UI project type is available in the InstallShield. The Suite/Advanced UI project type is available in the Premier edition of InstallShield. For information about the differences between these two project types, see Advanced UI Projects vs. Suite/Advanced UI Projects.
If the Click event of a navigation button includes either a Set Active Page action or an Install action, and if that action moves through the wizard interface, this prevents the default behavior described above. The default behavior is prevented even if the scheduled action is skipped because of a false condition for the action.
For example, you may want to override the default behavior for the Install button: instead of moving to the next wizard page in the interface, you may want the installation to proceed to a specific wizard page. In this scenario, you must add an Install action to the Install button’s Click setting, and specify the specific subsequent page. If you then add a condition to the action, and the condition prevents the Install action from running, the default behavior for the Install button is suppressed. That is, the installation does not start when the end user clicks the Install button. (Note that in this case, you may want to define a condition for the navigation button’s Enabled setting to ensure that the Install button is disabled if appropriate. Otherwise, end users may become confused when they are able to click an Install button that has no effect.)
Note that extension DLLs actions cannot prevent the default action except by actually calling the corresponding methods on the ISuiteUIExtension interface. The Advanced UI or Suite/Advanced UI engine cannot determine whether the extension chose to call the method. If you need an extension action to override the default behavior, but only navigate or install under certain conditions, add a Set Active Page or Install action with a false condition such as the empty None group.
See Also