This is a common interface conundrum. One solution that neatly skirts the line between intrusive and ineffective is to show an error indicator when the entry is invalid. You can then disable any action button (like OK) if there are any error indicators showing. A mouse over popup can then be used to show an error message and suggest a way to resolve the error.
A problem with "correcting" values is that where one value range depends on another value it can get really hard for a user to get all values to the state they want. Using the error indicator trick means values can be edited in any order and transient bad states simply don't matter.
Premature optimization is the root of all job security
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
