RE: [WiX-users] Enable/Disable PushButton based on Edit control state

[Stefan K. <skr...@in...>]

Another option would be to leave the Next button enabled and display an
error message box if required fields are empty. A variation of that would be
switchiung to a similar dialog ("twin dialog") that looks identical to the
dialog with the edit boxes, but has notes next to the empty/invalid fields
(static taxt boxes that are conditionally shown or hidden). That would be
somewhat similar to the user experience in registration forms on the web.


Kind regards,
Stefan Krueger
Microsoft Windows Installer MVP

Windows Installer FAQ
 <http://www.msifaq.com/> http://www.msifaq.com -  <http://www.msifaq.de/>
http://www.msifaq.de

InstallSite - Resources for Setup Developers
 <http://www.installsite.org/> http://www.installsite.org
 <http://www.installsite.de/> http://www.installsite.de (GERMAN)   

  _____  

From: wix...@li...
[mailto:wix...@li...] On Behalf Of Bob Arnson
Sent: Saturday, December 31, 2005 6:58 AM
To: Chris Putman
Cc: wix...@li...
Subject: Re: [WiX-users] Enable/Disable PushButton based on Edit control
state


Chris Putman wrote: 


Okay, I've been trying to figure out a way to have a dynamic enable/disable
condition on a "Next" button based on multiple Edit controls having
something other than an empty string in them. Now I can get that to work,
but it's clunky in that the Property associated with an Edit control is not
updated until the control loses focus, which only happens when the user tabs
out of the Edit control or clicks in another Edit control, or clicks on one
of the enabled buttons (in this case "Back" or "Next", neither of which is
appropriate). Well I can tell right now that once a user has filled in the
final Edit control, they'll expect to be able to click on the "Next" button,
problem is the button won't be enabled until they do one of the above. From
a user-interface perspective, this is a "bad thing".
 
So is there another way to have my "Next" button remain disabled and then as
soon as at least one character is entered into the Edit control, to enable
the "Next" button without having to force the user to tab out or click on
one of the other controls? Likewise, the instant the user deletes the last
character in an Edit control to disable the "Next" button. Right now the
user can click on the "Next" button in this scenario, but the instant they
do, the Edit control loses focus, the "Next" button disables, and nothing
else happens leaving the user to wonder, "What the hell?"

Not that I'm aware of. MSI's UI support isn't exactly robust, if you want
something "fancy." One approach, if it fits the user model of what's
happening, is a "Verify" button. That works for something like checking
server availability, where users expects to have to initiate it, but doesn't
work well when they'd expect it to happen on the fly.