I have recently started using the UltraComboEditor and have noticed an un-desirable 'bug' of the control.
I initialize the control in the designer as follows:
this.uceDepartmentHeadName.DataBindings.Add(new System.Windows.Forms.Binding("Text", this.bdsTop, "DepartmentHeadName", true));
this.uceDepartmentHeadName.DataBindings.Add(new System.Windows.Forms.Binding("Value", this.bdsTop, "DepartmentHeadID", true));
this.uceDepartmentHeadName.DataMember = "ttwDepartmentHead";
this.uceDepartmentHeadName.DataSource = this.pdsFillLists;
this.uceDepartmentHeadName.DisplayMember = "DepartmentHeadName";
this.uceDepartmentHeadName.ValueMember = "DepartmentHeadID";
When I run the program and proceed to change the text of the control by typing something that is NOT in the itemList of the control, the control will NOT give up focus. That is, if I try to click to another control the UltraComboEditor will still have the focus. The only way to reliquinish the focus to another control is to select an item from the UCE's list.
If I remove ONE of the two bindings from the control I do not get this behaviour... Is this a bug? If not, why is it behaving this way and how can I alter this behaviour?
I'm not sure if this is the problem, but the code you have here doesn't make much sense. The Text and the Value of a combo are dependent on each other, and binding them both at the same time is a contradiction. You should probably only be binding the Value and not the text.
What's probably happening here is that when you change the text in the control, it's trying to write both changes back to the data source and one of them is being rejected.
Thanks for the reply.
I've always bound the Value and Text columns simultaneously of the Microsoft ComboBox and I've never had a problem... Maybe I'm mistaken but I don't see the contradiction.
If I have a table with DepartmentHeadName and DepartmentHeadID I want both these to change, to change one and not the other would not make sense then what is the point of the comboBox?
The ComboBox has a Text and a Value. The Text is what the user sees and the Value is hidden (same as my DataTable the DepartmentHeadID is useless to the end user so we hide it)... but if the user Changes to a different list item I would want both the DepartmentHeadName to change as well as the ID. If we only bound the Value and not the Text it would not make much sense.
This is how the Microsoft version of the ComboBox was meant to be used, but please correct me if I'm using this control incorrectly.