In article <411781.78617...@web59815.mail.ac4.yahoo.com>,
"little.forest" <little.for...@ymail.com> writes:
> How is Control condition supposed to work?
For the most robust results, I use combinations of show *and* hide
actions with mutually exclusive conditions.
> I've this code:
> <Control Id="MigrateSettingsCheckBox" Type="CheckBox" X="20" Y="220" Width="
290" Height="17"
> Property="MIGRATE_SETTING_CHECKBOX_VALUE" CheckBoxValue="1"
> Text="Migrate settings from old version." >
> <Condition Action="show">Not Installed and NEED_MIGRATE_SETTING</Condition>
> </Control>
In your case you don't provide a value for the Hidden attribute on
your <Control>, so it is shown by default. Your nested <Condition>
specifies additional logic about when the control should be shown,
but no logic about when the control should be hidden.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
