Chris Barker wrote:
This is really a question of how much you think a UI should
hold the users hand. I don't like hand-holding, but I'm
probably not a typical user either.
To each, their own, I guess. I want my GUIs to be foolproof, if
not DAMN foolproof; if they're supposed to type an int, IMO,
they should type an int! 
I have a similar example, though more egregious:
On MacOS (before X), you need to set the amount of memory an app will
use (this is a bad thing, but was OK for 1984). You are given
two boxes
to fill in:Minimum size
Preferred size.Minimum size must be less than or equal to the Preferred
size, which is reasonable enough, but if you made the minimum
size larger, before making the preferred size larger, it would
give you an error, and re-set the minimum size. You had to
change the preferred size first. This drove me crazy! I should
be able to change it in any order I want, and only get an error
if I try to close the dialog with something wrong.
To do this with wxIntCtrl, I would make changes to the Minimum
size control dynamically set bounds for Preferred size control,
but not limit the values of the latter control. This way, you'd
get visual indication that you weren't quite done yet,
(preferred colored in red until the preferred was at least >= max),
but it wouldn't stop you from making the value whatever integer
you wanted. You could then add code in your form's validation
to ask:
if not preferred.IsInBounds(): ...
(See the demo code for example.)
Anyway, I've pontificated enough. It looks like you've done some
nice work that we can all learn from, even if we disagree about
the details.
Thanks!
/Will Sadkin
Parlance Corporation