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
- :
- Suite Feature Selection Tree Question
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
‎Dec 15, 2011
09:54 AM
Suite Feature Selection Tree Question
Is it possible to not allow the unchecking of features in the Feature Selection tree when in Maintenance Mode?
The reason is that this is a bit confusing to the user. Say we have 5 features and features 1 and 2 are already installed. When the user goes into maintenance mode they may say... I only want to install feature 3, so they uncheck features 1 and 2 and check feature 3. You see what's going to happen... features 1 and 2 are going to be uninstalled and feature 3 is going to be installed!
I think I would prefer not to let users uninstall from here.. they should got to ARP as they are accustumed to doing. I tried setting 'Remove' to No on the package, but then they can't install all the packages by uninstalling the Suite from ARP.
Another alternative would be to make the feature 'Not Visible' if it is already installed, but the only choices are Yes or No. Any ideas?
Thanks.
The reason is that this is a bit confusing to the user. Say we have 5 features and features 1 and 2 are already installed. When the user goes into maintenance mode they may say... I only want to install feature 3, so they uncheck features 1 and 2 and check feature 3. You see what's going to happen... features 1 and 2 are going to be uninstalled and feature 3 is going to be installed!
I think I would prefer not to let users uninstall from here.. they should got to ARP as they are accustumed to doing. I tried setting 'Remove' to No on the package, but then they can't install all the packages by uninstalling the Suite from ARP.
Another alternative would be to make the feature 'Not Visible' if it is already installed, but the only choices are Yes or No. Any ideas?
Thanks.
(23) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 17, 2012
07:58 AM
Is there any update to use boolean logic?
Example :
FeatureSelection -
Install button -
Enabled property -
{Binding FEATURE[featurename1].actionState!=0} AND {Binding FEATURE[featurename2].actionState!=0} AND {Binding FEATURE[featurename(n)].actionState!=0}
Example :
FeatureSelection -
Install button -
Enabled property -
{Binding FEATURE[featurename1].actionState!=0} AND {Binding FEATURE[featurename2].actionState!=0} AND {Binding FEATURE[featurename(n)].actionState!=0}
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 17, 2012
10:12 AM
No, this is still missing. You can usually get the same effect by writing a C++ UI extension action to summarize your more extensive logic into a new property, and wiring it in at a convenient location (such as a validation event - at least in 2012 Spring - or a next button in either version).
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)