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: Coding Behind a Button
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
‎Aug 28, 2007
04:27 PM
Coding Behind a Button
I have just started using InstallShield 2008, trying to make my first msi and have run into issues. This one might be a very simple answer. I am creating a custom dialog nad have added a button, but can find no way to code behind it. Where would I go to code behind this button to define its action when pressed?
Rick
Rick
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 28, 2007
08:57 PM
I'm interested in this topic as well. The answer to this will probably help me figure out how to fix my own problem. (I added a combobox to an existing dialog and don't know how to update the value of a memobox based on the user's selected value...)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 29, 2007
12:09 PM
For a Basic MSI, in the Dialogs view, select Behavior and then the control.
For an InstallScript or InstallScriptMSI project, you need to script the behavior.
I'd suggest first reading through the help material on custom dialogs, if you haven't already.
For an InstallScript or InstallScriptMSI project, you need to script the behavior.
I'd suggest first reading through the help material on custom dialogs, if you haven't already.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 29, 2007
01:31 PM
You'll probably get better help with a more specific question. 🙂 What is that you're trying to do? An MSI is fundamentally a database, and not script-based, so your best solution may or may not be code writing.
Best wishes!
Best wishes!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 29, 2007
10:28 PM
Think of ControlEvents as the controls Clicked Event. It's an observer pattern that creates a delegate of sorts by using the DoAction control event to call a custom action or perhaps a NewDialog to call the next dialog.
It's a declarative language and you try to not to write `code` unless required.
It's a declarative language and you try to not to write `code` unless required.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)