Autocomplete Bug in Ver. 4.1 Beta MultiColumnComboBox

Version 4.1 Beta of the MultiColumnComboBox appears to have inherited a bug present in 3.3.x. Specifically, the autocomplete feature malfunctions under certain conditions. To see this, run the MultiColumnComboBox Demo in the "Editors Package" of the 4.1 samples. While running, change the properties, via the property box to: DropDownStyle -> DropDown MatchFirstCharacterOnly -> False DisplayMember -> CompanyName //makes it easier to see the prob. Now, with the editbox fully selected, type in "Wq". At this point, there is no match and the control appears to permit a unique string to be entered. But then, enter "a" followed by "l". This incorrecly matches with Alfreds Futterkiste in the list box, but the editbox contains the leading "wq" characters and loses the "a". Is it possible to have this fixed before the 4.1 "release"? Thanks, Van Baker

Hi Van, Thanks for your feedback and your continued interest in Syncfusion products. I have notified the development team in this regard and have logged a bug report with the highest priority. We will try our best to resolve this issue before our final release.You can track the progress of the bug fix through the following link. Issue with AutoComplete in MultiColumnComboBox Sorry for any inconvenience caused. Best regards, Anu

Anu, This is one of several problems I have found with the MultiColumnComboBox. This is (IMHO) one of your most valuable controls and I use it extensively, so I''m glad to report any issues I come across. I''m surprised there aren''t more people using it than apparent by the amount of posting about it. Anyway, I clicked on the link you provided in your reply, and found some rather curious information under "Related Issues" in that link. Defect #838: It says: Resolution: This issue has not been resolved. Status: Closed (No Code Change): This issue has been resolved but does not require a patch. Please see the Resolution section for more details. Defect #815: This issue says: Resolution: This issue has not been resolved. Status: Closed: This issue has been resolved. You might want to update the status of these issues to reflect the current situation. Thanks, Van Baker

Hi Van, I apologize as those Defects seem to have been updated incorrectly. I''ve taken a look at some of our internal records, and the resolutions for them are as follows: 815: Fixed in 4.1 (I haven''t verified this personally) 838: This is controlled by the MultiColumnComboBox.CaseSensitiveAutocomplete property. (I''m not sure when this property was added, but I think it might have been between 3.0.1 and 3.2.1) Regards, Gregory Austin Syncfusion Inc.