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
- :
- Conditions for actions in Suite / Advanced UI project?
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
‎Mar 26, 2013
08:59 AM
Conditions for actions in Suite / Advanced UI project?
Is it possible to apply conditions to actions in Suite / Advanced UI projects? I'd need to have a checkbox at the wizard page, have the checkbox set a property and then if the property has a certain value, have a DLL action triggered when the Next/Finish button is pressed on the wizard page. If I assign the action to the checkbox itself, the action is triggered immediately when checking the checkbox, which isn't quite how users expect checkboxes to work. I'm fairly sure this is possible, but I can't spot the right syntax.
9 Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 28, 2013
05:24 AM
Is it really so that there's no support for conditions in {ActionDLLName::FunctionName} actions? Something like the {Install InstallationProgress,MyProperty==MyValue} in {Install Wizard_Page} actions or {Open {MyReadMeProperty},{MyProperty==MyValue}}
in {Open File_Or_URL} actions would be really useful also for {ActionDLLName::FunctionName} actions, but at least those syntaxes don't seem to work. Is there any way to achieve this functionality?
in {Open File_Or_URL} actions would be really useful also for {ActionDLLName::FunctionName} actions, but at least those syntaxes don't seem to work. Is there any way to achieve this functionality?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 01, 2013
01:30 PM
Unfortunately, not directly. Since in this case you're calling an extension, you could bake the condition into your extension code. But if this is a fairly generic bit of code that might get ugly fast. We've got some changes around the corner that will make things like putting conditions on actions more uniform (and should also address the {Mode ...} in the Visible condition thing you hit in your other thread).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 02, 2013
02:02 PM
Thanks for the info MichaelU. I ended up implementing the condition in a DLL as it was more or less an isolated control. It's good to hear that improvements are coming soon. Is there any chance that e.g. features could be conditionally disabled from the custom setup menu without building extensive hardwirings using a DLL?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 08, 2013
09:30 AM
Are you asking for a way to put a condition on the Visible setting of a suite's feature? (The generic Condition setting on the feature already allows you to select or unselect it by default.)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 09, 2013
01:28 AM
MichaelU wrote:
Are you asking for a way to put a condition on the Visible setting of a suite's feature? (The generic Condition setting on the feature already allows you to select or unselect it by default.)
Yes, or even better would be a way to disable features that are invalid for the given scenario. Pretty much similar to needs in this topic: http://community.flexerasoftware.com/showthread.php?203063-Suite-Project-Controlling-Feature-visibility
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 09, 2013
06:15 AM
If I can add to the wish list...
In a Basic MSI project under Releases I can enter a Product Name so that I can have a separate name for each release.
I don't see that same capability in a Suite project. Sure would be nice to have that!
I guess we would need to be able to override the Suite Guid just as we can override the Product Code for Basic MSI projects.
While we are at it.... it might be nice to be able to set different colors for each Release for Header, Body, Footer, etc... but I can live w/o that
Thanks for listening.
In a Basic MSI project under Releases I can enter a Product Name so that I can have a separate name for each release.
I don't see that same capability in a Suite project. Sure would be nice to have that!
I guess we would need to be able to override the Suite Guid just as we can override the Product Code for Basic MSI projects.
While we are at it.... it might be nice to be able to set different colors for each Release for Header, Body, Footer, etc... but I can live w/o that
Thanks for listening.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2013
10:05 AM
Okay, I'll see when we can do something about making Visibility of a feature conditional rather than a flat yes/no. This is being tracked on IOA-000072821.
Ron, it looks like your request was already entered as IOA-000077862.
Ron, it looks like your request was already entered as IOA-000077862.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2013
05:08 PM
Michael,
Great! I will look forward to that.
Thanks
Great! I will look forward to that.
Thanks
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 11, 2013
12:27 AM
Thanks Michael, sounds good!
