The following table lists and describes all the keys that can be used in the specification string.
The field will accept only numerals.
The field will accept only hexadecimal numerals, that is all numbers from 0-F
The field will accept only alphabetic characters. Numerals and punctuation marks will not be accepted.
The field will accept alphabetic characters and numerals but no punctuation marks.
field will accept any input
This key is only legal for specifying the editing length of
fields. If used, the field imposes no length restriction on the text entered.
Setting Field Content
Like all other input fields the rule input field can also be pre-filled with data and as usual, this is accomplished thought the
set attribute. As you might expect, the details of setting this field are rather on the complicated side. In fact you can set each sub field individually and you can leave some of the fields blank in the process. The
set specification for all sub fields is given in a single string. Each field is addressed by its index number, with the count starting at 0. The index is followed by a colon ':' and then by the content of the field. The string "0:1234 1:af415 3:awer" would fill the first subfield with
1234, the second one with
af415 and the fourth with
awer. The third subfield would stay blank and so would any additional fields that might follow.
You can provide runtime validation for user input into a text field and rule field via the
validator element (which is a child of the
field element). There are several types of validators already provided: