jlarson1.5524947125747598E12 asked a question.
Things I would like to be able to do:
1. Allow only 1 checkbox to be checked.
2. If 32 bit, not allow 64 bit checkbox to be checked.
Clues on how to do this?
:confused:
Are you sure you want to cancel the case creation?
Activity: Status change: 2 hours ago
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
As for conditionally disabling one of them, see the Enable setting of your check box or radio button. I'll have to get back with more information on what you can use here to implement the 32-bit vs 64-bit OS condition.
1. Feature1 64 bit
2. Feature2 32 bit
I want to be able to disable 1 if 2 is checked, etc. They should be able to install only one or the other, not both.
I think I would suggest an alternative approach, along the lines of an InstallationType dialog where you have multiple buttons that branch your installation. For example you could have an "Install the 32-bit version" and an "Install the 64-bit version" command link button, and disable the latter on a 32-bit system. Would this suit your needs? If so I'll try to work out how we can make that possible.
Thanks
FEATURE[feature name].actionState==install
where feature name is replaced with each feature's name. Then when the button is clicked, the associated feature will be set for installation.
If you'd rather put these on checkboxes and have them enable and disable like you mentioned before, specify the Property setting as above, and also specify an Enabled setting similarly:
{Binding FEATURE[other feature name].actionState==}
where other feature name is the name of the feature that should cause this feature's checkbox to be disabled. Watch out though; with this condition, if both features get enabled, neither can be disabled.
FEATURE[feature name].actionState==install
for Property versus doing
{SetProperty FEATURE[feature name].actionState=install}
for Action?
It is a bit annoying that the syntax is not consistent.
I REALLY would have expected that there would be more documentation available about Suites from Flexera by now. I don't think that anyone can argue that those of us that have used the Suite feature have struggled with A LOT of trial and error! Yes, yes, I know... standard answer is read the blogs. And when that does not contain the info you need?????
{Binding P==V} functions differently on, say, a check box. It shows the check box as checked if the property P has the value V. Clicking the check box when checked will reset the property to empty; when unchecked, it will set the property to V. On a pushbutton, it will merely set P to V whenever it is clicked.
{SetProperty P=V} as an action works just like the pushbutton case, although I'm unclear off the top of my head if it also fires when the radio button is clicked to clear the check box. Note that, particularly in a check box or radio box, you can have both; {Binding P==V} and {SetProperty Q=R}, so two properties can get set in one click.