Raise CellValueChanged from a custom editing control in a DataGridView

Question

I have a DataGridView (WinForms) in which I have defined a custom EditingControl derived from DataGridViewTextBoxEditingControl that only allows numeric characters.

I need to raise CellValueChanged event on the DataGridView each time the user press a key, but the default behaviour is to raise the event only when edition has been completed.

How can I raise the event each time a key is pressed?

public class DataGridViewNumericTextBoxEditingControl : DataGridViewTextBoxEditingControl
{
    protected override void OnKeyPress(KeyPressEventArgs e)
    {
        e.Handled = Char.IsLetter(e.KeyChar);
        if (!e.Handled)
            RaiseDataGridViewCellValueChanged(); // <-- Any way?
    }
}

Update:

I've found a workaround, but I'm not sure it's a good solution:

public class DataGridViewNumericTextBoxEditingControl : DataGridViewTextBoxEditingControl
{
    protected override void OnKeyPress(KeyPressEventArgs e)
    {
        e.Handled = Char.IsLetter(e.KeyChar);
        if (!e.Handled)
        {
            EditingControlDataGridView.EndEdit();
            EditingControlDataGridView.BeginEdit(false);
        }
    }
}

Answer 1

What is the goal here? It appears you are attempting to create a keyboard mask, where any non confirming character raises an alert? If so, you may find happiness in the DataGridView by adding a MaskedTextBoxColumn. A MaskedTextBoxColumn controls the input in a much more reasonable way than forcing edit commits.

See here for code that shows how to use it: http://msdn.microsoft.com/en-us/library/ms180996.aspx

According to your updated criteria in the comments, it sounds like your solution is probably about as good as it will get. Realize, however, that it is very easy to get into infinite event loops when you have other controls updating on another based on keyboard events. You are probably best served to have a single delegate on the form that handles all of the events as it can prevent infinite loops of event triggers by discarding spurious events them based on state.

Effectively this would be using the Model View Presenter pattern, where your delegate acts as the presenter and manages the traffic on your View (your UI).

Doing this, you can even move the Presenter logic into a new class that you then data bind to, allowing you complete control over the UI from one logical construct, rather than a hodgepodge of event handlers.