Another user with 'combox does not always return altered val

Hi - I’ve been having the same issue as Kris A reported (thanks for the great controls BTW). I’ve found that if I use a combo box with filtering enabled then I have to exit the combo control (eg., tab off of the control) if I type in new text rather than select a predefined value from the drop down. For example, in the following html, if you enter unique text in the Memo control (say ‘DDD’) and hit the Execute button with the mouse, then I get a memo must be defined alert. After clicking on the alert if I hit the execute button immediately afterward, then the new text DDD will be seen and displayed. If I enter new text (eg., EEE) and tab off of the control until I get to the execute button and press spacebar to submit then the EEE is immediately displayed. I assume it has something to do with the event ordering and trigger associated with lost_focus event or the like but haven’t been able to find a solution… any help is very much appreciated! (tried in IE7, opera, and safari/win, btw).



Couple other questions/observations as well:



1) even though there are only 2 entries in the combo select, the control shows 2 additional white space rows below the defined entries - is there any way to not show those?



2) noticed a difference from the drop down options when running in a popup window vs standard select - the dhtml combobox only shows options that fall within the window while the standard select drop down options can extend beyond the window edge - assume there’s nothing that can be done about this but thought I’d ask anyway,



Thanks,



-Bob









combo



































Memo:















Test 01

Test 02


























is there any way to not show those?
The height of combo defined in dhtmlxcombo.css , you can adjust such value directly through css rule

.dhx_combo_list{
position:absolute;
z-index:230;
overflow-y:auto;
overflow-x:hidden;
border:1px solid black;
height:100px; //<= this is it

or use optional dhtmlxcombo_whp.js extension , which adds support for the
combo.enableOptionAutoHeight(true);

>>2) noticed a difference from the drop down options when running in a popup window vs standard selec
The combo is a part of window, so it can’t be rendered out of its borders ( but you can adjust direction of combo opening, to minimize bad effects through combo.enableOptionAutoPositioning(true); )

with lost_focus event or the like but haven’t been able to find a solution
In your case , the onclick event fire before “focus out” for the combo, so the combo has no time to updates its value. You can try to assign the next code line to the onclick event of button so it will be executed before any other logic
<input onclick=‘combo._confirmSelection();