Start Building Professional
Web Apps Today

Combobox Options

I really like the combo boxes you guys develop. I am trying to work through some final kinks.

Sometimes the ajax request comes back after I have moved on to another element on the form. Take US cities for example. There are over 17K records, so it may not come back fast enough. Is there a way to not have the expand window show on city, if the focus is on another element? It doesn't make sense to prompt the user on city when they have finished, and have moved on.

Next, if you load a list from XML data, it does not let you set the value of the combo, it errors out.
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLInputElement.setSelectionRange]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: /dhtmlx/dhtmlxCombo/codebase/dhtmlxcombo.js :: dhtmlXRange :: line 977" data: no]

On a read only combo, would also be nice if you could scroll through the options by typing B, and have it jump to the B entries. And on further presses of B, it moved through the list of items that start with B (like normal combos).

Are there any plans on support optgroup? This comes in really handy when you want to use 1 combo box instead of 2. For example you have a main category and then a subcategory within one combo. Here is the standard html code:

<select id="officeItemList"><option value="1">eraser</option><option value="3">pencil</option><option value="4">ruler</option><option value="5">ink</option><optgroup label="paper types"><option value="7">A4 paper</option><option value="8">A3 paper</option><option value="9">letter-sized paper</option></optgroup><optgroup label="chair types">    <option value="10">executive</option>    <option value="11">janitor</option>    <option value="12">developer</option></optgroup></select>

I appreciate the support!

Kevin

>>Is there a way to not have the expand window show on city, if the focus is on another element?
This issue already fixed in inner build ( it will be released on next week )
You can try to use attached js file instead of original one - it must resolve issue.

>>Next, if you load a list from XML data, it does not let you set the value of the combo, it errors out.
Unfortunately the issue can't be reconstructed with local samples.
In theory it can be caused by usage of readonly combo in filtering mode ( which seems as not really usefull combination, because filtering need direct key input to be used )

>>On a read only combo, would also be nice if you could scroll through
With latest version of combo, in case of readonly mode - the combo will scroll to first entity started from typed letter.

>>Are there any plans on support optgroup?
It may be usefull feature, but we have not plans to support such feature in oncoming build. But it will support different king of grouping, which will allow to group few combos ( when changing value in one , will automatically adjust others )

So far so good, the combo is acting much better with the update.

I will play around with the XML load on this new version, and if it is still broken, I will send you code on how to duplicate.

It is very nice that when typing "G" it jumps to the G items.  Can we have it iterate through items starting with "G" upon further g key presses?

Thanks for the support!