Hi all,
I created a custom dialog...
I have a button control that is disabled/enabled whether or not some text
box controls are empty or have some text in them:
<Condition Action="disable"></Condition>
<Condition Action="enable"></Condition>
Here is one of my text box controls:
<Control Id="textBoxUsername" Type="Edit" Height="14" Width="177" X="180"
Y="159" Property="DATABASE_USERNAME" TabSkip="no">
<Condition
Action="disable">DATABASE_WINDOWSAUTHENTICATION="1"</Condition>
<Condition
Action="enable">DATABASE_WINDOWSAUTHENTICATION="0"</Condition>
</Control>
I have a button control that is disabled if any text box is empty, if I type
text in a control the button won't be enabled until I click into another
control...
The text box control seems to think it is empty until you click into another
control...
On the flip side, the button control isn't disabled if I empty the text box
control until I click into another control...
Has this been logged before? Or did I do something incorrect?
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-Disable-a-control-because-another-control-is-empty-enter-text-control-is-not-enabled-tp7581117.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
