*meekly raises hand.. I think my original intention was to change some of the default error messages to give more specific information about the format that we want the input to be in. Rather than just saying "your input sucks, try again" and having them randomly type stuff in until they get it right.
Perhaps the messages need to be looked at a little more closely on an individual basis, or ideally find some way to translate "#" type number format patterns into a more human friendly message ? On 11/29/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
Hi, Is there any particular reason why the number format message in the number validator changed in 4.1? It used to be: "<Field> must be a numeric value." And now is: "<Field> must be a numeric value. Format is #." It's not clear to me that adding this format message is going to be beneficial to any of our end users. I'm guessing there's a good reason it was added though. I'm just trying to figure out what it may be. Thanks, Kevin -- Kevin Menard Servprise International WebReboot -- Remote Reboot Without Pulling the Plug 800.832.3823 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
