I have a problem when using enableFilteringMode where the input to the combobox will auto-populate with the first item retrieved and put the cursor at the end of the item instead of “guessing” the first option and highlighting it, allowing the user to continue typing after the previous letter they typed like in your example here.
There is a standard behavior of our combo - the behavior you mentioned.
Describe in detail, what is not pleasant to you (the description on points with images) and that you want to have as a result.
As you can see in my combobox, the guessed word is thrown in the input, but the cursor is put at the end of the word (not desired behavior).
However, in your combobox, the guess word is thrown in the input, and the cursor is the rest of the guessed word (‘bbreviture’ in this case) instead of being moved to the end.
I’m wondering why my combobox moves the cursor to the end of the word instead of highlighting the untyped portion of the guessed word to allow the user to continue typing after the first letter typed.
I have version 3 of the combo. Also, I am creating a combobox from an existing select box (dhtmlXComboFromSelect) instead of creating a new combobox from a div like in the example. I am working on creating a demo for you.
Is there any way to do this outside of a JSON object, or do I have to use the JSON object? Can I create an li of type combo in UL initilization or an item of type combo in an XML initialization?
The reason I don’t want to use a JSON is because I cannot define a className on a list (dhxlist_base) which prevents me from customizing the css. I suppose I could use a fieldset, but I would prefer to not have to wrap all my different form elements in fieldsets.
You can use my second attached approach WITHOUT json.
myForm = new dhtmlXForm("form1");
myForm.loadStruct("dhxform_combo.xml", f1);
function f1(){
combo = myForm.getCombo("mycombo");
combo.enableFilteringMode(true);
combo.setComboText("");
}
And this way will allow you to avoid using json.
Thank you for your help. I was continuing to run into issues because I referenced the javascript files in an order different than yours. Once I rearranged my calls, I was able to see the desired functionality.