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

In reply to Re: Tk Entry validation conundrum by GrandFather
in thread Tk Entry validation conundrum by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.