Does Austria use cents?
What you are suggesting violates WYSIWYG. The person won't know how the
input is read until after they are out of it (too late!) Also, showing the
formatting can be used to make sure it gets entered correctly (Any DBA will
use YYYYMMDD, US uses MMDDYY and Europe uses DDMMYYYY.
You (and I) are also in the minority. We actually know keyboard shortcuts.
and prefer keyboard to mouse. We think ncurses is fine
There is no 10-digit zip in the US. It's Zip+4 as It's called. (I believe
the 4 is actually a road number. ) So Zip (5)+4=9. We do use 10 digit
dialing though. AAAEEENNNN.
I have come up with a cool way to do date (any really) validation. Assign a
separator char (i.e. '/') then assign the mask. When this happens create an
internal array with length=#ofChunks (=seps+1). These individual chunks can
then be assigned chunk[0].valid_vals=range(1,12);
chunk[1].valid_vals=range(1,31);chunk[3].valid_vals=range(1900,2100) - or
enumerate a list (Jan, Feb, Mar...Dec)
The problem with this is dates are inherently complex numbers. February may
be 28 or 29 days, depending on the year. So I think we'll need a special
mask for that (MM-DD-YYYY) that one exception aside, in general I think
these capabilities would be very useful. Additionally you might want to
implement something like a virtual function to perform custom validation.
Finally, and this one is la crème de la crème, if any chunk is enumed or
ranged() (within reason) could there be a drop down list provided?
(Essentially an integrated combo box)
Places where this could be useful: (Warning, I'm not the best at examples
;-))
IP address selection. Assume you have a list of valid IP addresses
(11.11.11.11 to 11.11.11.20 and 22.22.22.1 to 22.22.22.10) You could provide
4 drop downs, with the first being (11,22) the OnValidate would run and if
the user selected 11, then .11.11. would also be filled in (because then in
each category the # of choices is 1, in editable*-combo box) then on the
last one because there's more than 1, a combo box of (11-20).
* this brings up a point. I am a firm believe that the user should be able
to have ultimate control. They should be able to enter anything as long as
it's not illegal (i.e. Feb 30th is illegal) Therefore, each chunk needs to
have a constraint of something like 'enforce' or 'suggest' So I could but in
23.244.233.22. The validation routine would then have to make sure that each
chunk is less than 256 too.
I know it's a lot, and I don't expect it any time soon, but I'm putting it
out there to think about.
···
-----Original Message-----
From: Chris Munchenberg [mailto:cjm@ava.com.au]
Sent: Friday, February 14, 2003 8:38 AM
To: wxPython-users@lists.wxwindows.org
Subject: Re: [wxPython-users] wxMaskedTextCtrl 0.0.4 (with fries!)
My 2c on the subject.
Having not given it any thought till it came up on the list, I've been
looking at the systems & programs I use - what I like, what annoys the crap
out of me.
I like to click or tab into an empty control & just type. Apart from the
first couple of time I use something, I have a pretty good idea of what I am
going to put into it. I don't want to worry about cursor positions etc. If I
get it wrong, wait till I've finished then tell me. Trying to put the cursor
in between brackets, or at the left or right end etc is just beyond my
powers of concentration while I'm thinking about the quickest way to get out
of work. Version 0.0.4 works great with tabbing into the control, not so hot
with the mouse.
Date formats that don't accept almost any type of deliminator (eg 01-01-03 =
1/1/3 = 1.1.3 = 01 01 2003 etc) The control should fit my thinking, not the
reverse.
I prefer display formatting to take place after I've finished telling it
what I'm telling it. I expect people to shut up and listen when I'm talking.
It doesn't happen, so could I please get it from my computer?
Having said my piece, I love it so far. One thing I don't understand. In
Australia, we don't have zip codes. Does the US standard 10-digit zip only
use 9 digits?
Chris Munchenberg
----- Original Message -----
From: Jeff Childers
To: 'wxPython-users@lists.wxwindows.org'
Sent: Friday, February 14, 2003 4:58 AM
Subject: RE: [wxPython-users] wxMaskedTextCtrl 0.0.4 (with fries!)
Paul,
Thanks for the feedback. Everything helps.
Re: Overwrite vs. insert
-------------------------
I've thought about this. The way I have created the control, insert behavior
would have to be hand-coded and would have to contemplate handling
situations like a mask of AAA###. What happens when you insert into the
character region? I guess the characters would have to scroll just to where
the ### section starts, with the ###s not scrolled. Is this intuitive?
Anyway, I've put this off for a future version when a brainstorm suggests a
simpler way to handle this. Ideas and/or suggestions welcomed.
Re: StudlyCaps for MethodNames
-------------------------------
So noted!
Again, thanks for the feedback
Regards,
Jeff Childers
jchilders_98@yahoo.com
-----Original Message-----
From: Moore, Paul [mailto:Paul.Moore@atosorigin.com]
Sent: Thursday, February 13, 2003 11:31 AM
To: wxPython-users@lists.wxwindows.org
Subject: RE: [wxPython-users] wxMaskedTextCtrl 0.0.4 (with fries!)
From: Jeff Childers [mailto:jchilders@smartbusinessware.com]
For review: version 0.0.4 of wxMaskedTextCtrl.
Just had a quick look, out of curiosity more than anything else,
as I have no immediate need for the control.
But a couple of points:
1. I notice that overwrite mode is the default - is it possible
to switch to insert mode?
2. The method names - get_plainValue, for example - have a rather
strange use of case and underlines. I'd rather see it match the
wxPython standard, which is StudlyCaps, so we'd have
GetPlainValue...
But overall, it's very nice. Feel free to ignore the above comments,
as I say I probably won't need the control any time in the forseeable
future...
Paul.
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org