david adams wrote:
Yeah, that's what I get when I reply without enough coffee. Or with too much coffee.<g> Unfortunately, feature conditions aren't constantly evaluated so you can't use them to set feature levels based on properties set in the UI. From "CostFinalize Action" in the MSI SDK:If I set the Feature @Level="1" and use Condition #1 or #4 in an attempt to "disable" the other three, then all four features stay at level = 1 in CustomizeDlg (i.e. feature set for install).If I set the Feature @Level="0" and use either Condition #2 or #3 in an attempt to "enable" the selected one, then all four features stay at level = 0 in CustomizeDlg (i.e. feature not available). The CostFinalize action queries the Condition
table to determine which features are scheduled to be installed.
Costing is done for each component in the Component table. CostFinalize happens early. To add or remove features after that,
use the AddLocal/AddSource and Remove control events. -- sig://boB http://bobs.org |
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
