>Hi John,
>
>>Brings up the point... if your capturing all the Keystrokes.... Why make the control readonly?
>
>I know the technique sounds silly at first glance.

Not to me... it's calculator input. I've written controls for it too.

>>But, by keeping the control in a readonly state, the control's value STAYS right aligned while I manipulate the control's value during KeyPress event. This gives me a control that supports input while preserving right alignment.

But I don't see that the readonly state is needed for that, just trap all of the keypress events and use this.value = newval with NODEFAULT to input the value and it stays right aligned.

Or am I missing some situation where it doesn't stay alligned?

Dorin's control for instance stays right aligned for me without being readonly.