Hi,

I tested this out and I don't seem to be getting the same results you are describing.

To test this out, I put an UltraComboEditor on a form with a button. The button does nothing, it's just there so I can take focus away from the combo.

I populated my combo like so:

        private void Form1_Load(object sender, EventArgs e)
        {
            this.ultraComboEditor1.Items.Add(1, "A");
            this.ultraComboEditor1.Items.Add(2, "B");
            this.ultraComboEditor1.Items.Add(3, "C");
        }

Now, I run the application and type in a "1" into the combo and click on the button.

The combo shows an "A" and the ItemNotInList event does not fire.

So there are two questions:

1) Why is the combo showing an "A"?

The reason for this is because when you type an item into the combo that is not on the list, it has to do something with the text you entered. Normally, it would take what you typed in, find the matching display text and the Value property of the combo would return the matching value on the list. But in the case where there is no matching item no the list, the Text and the Value of the combo both return the same thing - the text you entered.

So when you enter a "1" and there is no item on the list with a DisplayText of "1", the Value and Text of the control get set to "1".

Now... since there is an item on the list whose DataValue is 1, the control translates this into a display text of "A".

The fix you mentioned was for a bug where when the text was not found on the list, the Value of the control was returning null. That was a serious bug that would prevent users from entering anything that was not on the list because when they did so, the Value would be null and then the Text would be cleared out, because there is no null item on the list.You would essentially lose what you typed.

So all of this is as it must be and I don't see any way around it.

2) Why isn't ItemNotInList firing?

This is where I see a problem. When you type a "1" and there's no matching item on the list with a DisplayText of "1", the ItemNotInList event shoudl fire.

What must be happening is that the value of the control has already been set to "1" and the "1" has been translated into an "A" before we determine whether or not to fire the event. This seems like it may be a bug and I'm going to forward this post over to Infragistics Developer Support so that this can be checked out.