I'm working on a superclass numeric entry field with a fixed max number of digits to the left and to the right of the decimal.

So far the field acts this way.

1. If the field is empty, digits are inserted until a '.' is entered and then as additional digits are entered they are placed to the right of the decimal until the the decimal max digits is reached and then moves to the next field.

2. If the field is not empty and the insertion point is to the left of the '.' it overwrites the digit below it. This occurs until it gets to the decimal point and then it starts to insert digits. If the insertion point is to the right, it just overwrites until the last position is reached and then moves to the next field.

3. If the user places the insertion point to the left of the decimal and presses the '.' key then all digits to the right of the insertion point are truncated up to the old decimal place and the field repositions so that the '.' is in the right place.

4. The Del and Backspace key do as you would expect.

5. The minus sign can only be entered only in the first position

6. Upon entering the field any commas are removed and when exiting commas are introduced.

7. Ctrl-F brings up a calculator whose final value is put into the field when the calculator is dismissed.

The windows calculator works a little different. It starts with 0. and each digit is inserted until you press the '.' and then all digits are entered to the right of the decimal. No arrow or insertion points are allowed.

I'm interested in what are really good standards for this type of entry. I'm wondering if I should disallow the arrows and/or the insertion pointer like the windows calculator does and how I would do that.

Our customers want heads down data-entry where the field fills and automatically moves to the next field etc.

Bob Mechler

So far the field acts this way.

1. If the field is empty, digits are inserted until a '.' is entered and then as additional digits are entered they are placed to the right of the decimal until the the decimal max digits is reached and then moves to the next field.

2. If the field is not empty and the insertion point is to the left of the '.' it overwrites the digit below it. This occurs until it gets to the decimal point and then it starts to insert digits. If the insertion point is to the right, it just overwrites until the last position is reached and then moves to the next field.

3. If the user places the insertion point to the left of the decimal and presses the '.' key then all digits to the right of the insertion point are truncated up to the old decimal place and the field repositions so that the '.' is in the right place.

4. The Del and Backspace key do as you would expect.

5. The minus sign can only be entered only in the first position

6. Upon entering the field any commas are removed and when exiting commas are introduced.

7. Ctrl-F brings up a calculator whose final value is put into the field when the calculator is dismissed.

The windows calculator works a little different. It starts with 0. and each digit is inserted until you press the '.' and then all digits are entered to the right of the decimal. No arrow or insertion points are allowed.

I'm interested in what are really good standards for this type of entry. I'm wondering if I should disallow the arrows and/or the insertion pointer like the windows calculator does and how I would do that.

Our customers want heads down data-entry where the field fills and automatically moves to the next field etc.

Bob Mechler

## Comment