Insufficient Data For Meaningful Response
But seriously: You seem to be looking for a contradiction - an edit field that will accept anything, but by "default" it should accept only numbers. So my first question is: how do you propose to permit the user to change
the input mode? My second question is: given that users are used to dealing with edit fields that accept the standard character inputs, why are you interested in violating their default understanding of how to enter data into an edit field?
If numeric characters are to be expected as the "default", that implies that your use of the information expects that - more often than not - numeric characters are the proper input information. Set the field to be numeric-only, and you're done. Why allow non-numeric? If you wish to permit all types of text entry, why restrict to numeric-only and then force
users to jump through a set of hoops to enter something different?
The standard, typical edit field (allowing all types of character input) is something that every user understands as a result of using them in every other application. If your edit field only allows numeric input (but can be switched, somehow, to allow all input), the users will need to know how to switch the mode (requiring some documentation to be read, or requiring a note on the screen telling the user what to do). My guess is this: if the mode setting can be saved from one launch of the app to the next, the first time the user sets it to "allow all", they will never
set it to anything else, even if the next time they use it they only want to enter numbers. Users will always find the quickest way to get their data-entry tasks done, and since they're already familiar (or should be
) with how to enter letters, numbers, and all the other characters using their device (full-keyboard or not), imposing a restriction on their input that can be changed if necessary seems (in my humble opinion!) to be a waste of coding and a waste of user time.
If your app is for you alone, or if this is an exercise to challenge your BlackBerry coding abilities, by all means, have at it. But if you're developing for a group of users (no matter how small), think about the constraint you're trying to impose and what that will mean for usability.