> The theory is that you should prevent choices that aren't really
> available. But in practice that is certainly also a fine solution, I
> think.
That's the theory, and it has some merit. However, is it less user-friendly
to show the OK button enabled when the user will not in fact be allowed to
submit the form if they press it, or to have the button disabled at the
beginning, then enabled when the user types something, then possibly
disabled again when they delete what they type, etc, with no explicit
explanation to the user of what causes the button to change states like
that. I think it's a toss-up.
Also, with the web, users have gotten used to buttons being enabled all the
time, and then having the form rejected when they try to submit it without
all the required data (usually with some visual indicators of what they need
to correct, like making the labels of the empty/incorrect fields BOLD RED).
So, in this case, I think it's an acceptable solution, and less work than
rigging up every single control to a button enable/disable method, using a
timer, and so on.
-Walter
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://www.realsoftware.com/listarchives/lists.html>
|