I have a combo box that was working fine before upgrading to IgniteUI 2014.1. I was using the selectionChanged event to determine when the value in the combo was changing and then doing some processing based on that. After upgrading to IgniteUI 2014.1, this selectionChanged event is fired immediately after typing a single letter in the combo box.
For example, if I have 2 items in the combo, "Active" and "Company", and I drop down the combo and type the letter "c", the selectionChanged event is fired immediately and the "value" on the control is "Active", even though I was going to type "Company". If I continue typing and finish "company" and hit enter to select that value from the drop down, it never seems to update the "value" to Company - and it performs the processing on my screen for "Active" field instead of "Company" field (even though drop down now has company in it).
Did something change in 2014.1 release for this? Is there a different event I should be using? I am creating the combobox via MVC and here is the code that is creating it:
comboBoxHtml = HtmlHelperExtensions.Infragistics(this.Helper) .Combo() .ID("mycontrolname") .Width("100%") .Height("25px") .AllowCustomValue(false) .CaseSensitive(false) .CompactData(false) // required for the item template .Disabled(false) .EnableClearButton(true) .FilteringCondition("contains") .FilteringType(ComboFilteringType.Local) .HtmlAttributes(customHtmlAttributes) .ItemTemplate("<div class='comboTemplate'>" + "<div class='comboInfo'>" + "<span class='emphasizedText'>${DisplayText}</span>" + "<div><span class='deEmphasizedText'>${" + (isDescUsedAsDisplay ? "Identifier" : "Description") + "}</span></div>" + "</div></div>" ) .NullText("field") .RenderMatchItemsCondition(ComboRenderMatchItemsCondition.Contains) .SelectedValues(null) .TextKey("DisplayText") .ValueKey("Identifier") .DataSource(metadataList.OrderBy(x => isDescUsedAsDisplay ? x.Description : x.Identifier)) .DataBind() .Render();
We are on a pre-release (2076 I believe) service release of 2014.1. We were on 2013.2 service release 2157 previously when it was working.
And yes, if I type a single letter, and there are multiple matches in the drop down, the selectionChanged event fires immediately upon typing that single letter.
Hello Ryan,
Thank you for contacting Infragistics!
I have done some looking into this matter and have some information and questions. First I tested this with v13.1 and I see that once the combo has 1 unique value it selected it and fires the selection changed event for each character you type once that is the case. What is the service release you are using for v14.1? You said you saw a different behavior in a previous version, what is that version number and service release? If you type to filter and still have multiple possible values does the selection changes event occur?