Hi,
I have a bounded Ultracombo having following items in the list.
ID Code--------------------1 A 2 B3 Ccombo is binded with a table having two columns, ID and Code. DisplayMember is Code and ValueMember is ID. Whenever we type any data that is not in the list then ValueChanged event is firing twp times. Lets say I typed D in combo then
First time UltraCombo.Value comes as null and second time it comes as the data I typed ( "D" ). This is happening in 9.1 version dlls.In 8.1 version dlls it was working fine ( ValueChanged event was firing only once ). We were using 8.1 dlls and out application was designed to check value null for invalid data. After upgading the dlls all these problems get started.. Its crashing our application..
Are you guys going to fix this bug?
Thanks,Dhananjay
Hi Dhananjay,
I just tested this out in a small sample project and it seems to work fine for me. The event only fires once.
I am attaching the sample I used so that you can try it out and see if you get the same results. If you do, then there's some other factor at work in your application that is causing this. Maybe a property setting or the handling of an event.
If not, then it's probably because I'm usinga newer build than you and you should get the latest service release.
Hi Mike,
Why ultraCombo.Value is coming as invalid data? in earlier version dlls if we type invalid data ( If ValueMember does not match ) then Value was coming null. now its coming as typed invalid data... I think, earlier functionality was correct.. combo.Text should come as Typed text and Value should be null because ValueMember did not match.. Do you guys fix this Or this is new feature...?
ThanksDhananjay
I'm not sure what earlier versions you are referring to. As far as I can remember (and I have been working here at Infragistics since before the UltraCombo existed), the control has always worked this way.
If you type in a value that is not on the list, the control's Value property returns the Text you typed in.
If you set teh DropDownStyle to DropDownList, then the user will be unable to type in an invalid value, and if you set the value in code to something that is not on the list, it probably returns null. But this behavior has not changed in any version as far as I know.
You might have not aware of that...Check the sample with Infragistics 8.2 version dlls. First select some valid value from the list then type invalid data and check the value.. it comes null.here is the sample code.private void ultraCombo1_ValueChanged(object sender, EventArgs e){ Debug.WriteLine(ultraCombo1.Value.ToString(), "ValueChanged");}private void Form1_Load( object sender, EventArgs e ){ DataTable dt = new DataTable( "Test" ); dt.Columns.Add( "ID", typeof( Int32 ) ); dt.Columns.Add( "Code", typeof( string ) ); dt.Rows.Add( 1, "A"); dt.Rows.Add( 2, "B"); dt.Rows.Add( 3, "C"); ultraCombo1.DataBindings.Clear(); ultraCombo1.SetDataBinding( dt, null);}execute this code with 8.2 version dlls.
Sorry, I guess I was thinking about UltraComboEditor. There are no such events on UltraCombo.If you don't need multiple columns in your list, you might want to consider using UltraComboEditor, instead of UltraCombo. I don't think this problem occurred in both controls.
Can't find any Before/AfterExitEditMode events for UltraCombo. Anyway, thanks a lot for the info.
I don't think there's any way to work around this.
You can try using the Before/AfterExitEditMode events.
There is no event that fires when the user is finished typing, because it's impossible for the control to know when they are "finished". You might be able to make use of the Validating event, which will fire when they try to leave the control.
But personally, I doubt that any of these events will help.
Any work around you may think of? I don't think by any chances our company will take the risk to upgrade it to v10.3.
May I know what is the event UltraCombo control fire when it out of the edit mode? Or may I know what is the event fire when user finished entering the text manually in the text box?
Thank you very much.
If the latest service release for 8.2 is not working, then there's nothing we can do. That version is over 3 years old and is no longer being updated.