This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: For a BasicMSI project, is it possible to define on-load event for a dialog?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 11, 2011
04:26 AM
For a BasicMSI project, is it possible to define on-load event for a dialog?
Hi,
After jumping to a new dialog, I want to do a CA automatically, without any end user operation, e.g. clicking button.
In the dialog before this one, I tried to put "NewDialog" before "DoAction", but the new dialog was not opened untill the CA was finished.
Is there any solution for this? Thanks.
After jumping to a new dialog, I want to do a CA automatically, without any end user operation, e.g. clicking button.
In the dialog before this one, I tried to put "NewDialog" before "DoAction", but the new dialog was not opened untill the CA was finished.
Is there any solution for this? Thanks.
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2011
02:46 PM
Hi There,
I think your only real option is an Asychronous custom action that waits for the window title to appear, and then take some action.
It will take some coding, however. Read up on FindWindow()
I think your only real option is an Asychronous custom action that waits for the window title to appear, and then take some action.
It will take some coding, however. Read up on FindWindow()
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2011
03:06 PM
Before I suggest a way-off-road solution, it would help to better understand what this custom action is going to do in the first place.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 16, 2011
08:04 PM
Cary R wrote:
Hi There,
I think your only real option is an Asychronous custom action that waits for the window title to appear, and then take some action.
It will take some coding, however. Read up on FindWindow()
Thank you. I will try it.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 16, 2011
08:10 PM
Christopher Painter wrote:
Before I suggest a way-off-road solution, it would help to better understand what this custom action is going to do in the first place.
The CA scans registry to find if there is any conflict between the installed software and the software that is going to be installed.
Originally, it was performed after end user clicks the "Next" button in the last dialog. Then they want the CA to be performed as soon as the current dialog is opened.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 16, 2011
08:17 PM
Is there a reason you can't use System Search ( AppSearch and Reglocator tables ) and Setup Conditions (Launch Conditions) to do the same task?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 17, 2011
02:17 AM
To be honest, my IS knowledge is limited. I have never heard about the search method you mentioned before.
The general idea of my IS project is:
1. Check software conflict.
2. User specifies installation information.
3. Start to install.
AppSearch is located in the beginning of installation sequence, but the installation sequence will not be started until the user clicks the "Install" button in "ReadyToInstall" dialog. Right?
The general idea of my IS project is:
1. Check software conflict.
2. User specifies installation information.
3. Start to install.
AppSearch is located in the beginning of installation sequence, but the installation sequence will not be started until the user clicks the "Install" button in "ReadyToInstall" dialog. Right?