For example, the check drop-down list has the following items:
A1, A2, B1, B2, B3, B4, C1, C2
When 'B' is typed in the drop-down's filter text box, the 'B1' becomes the first on the list. I then check-mark only the 'B2' and 'B3' items and close the drop down.
After a postback, in the code behind I then determine which items were checked.
It appears, that along with 'B2' and 'B3' items, the 'B1's Selected property also appears to be True.
This is unexpected, because only 'B2' and 'B3' were checked.
Am I using the right approach to determine the checked items in the list? If not, what is the appropriate way to do so?
<ig:WebDropDown ID="cboCarrierLookUp" runat="server" Width="280px" AutoPostBack="False" EnableClosingDropDownOnSelect="False" CurrentValue="<< type company name here >>" EnableMultipleSelection="True" DropDownContainerHeight="200px" DropDownContainerMaxHeight="200px" EnableCachingOnClient ="True" EnableCustomValues="True" EnableCustomValueSelection="True" Height="21px" PageSize="0" EnableClosingDropDownOnBlur ="False" OnValueChanged="cboCarrierLookUp_ValueChanged" DisplayMode="DropDown" AutoFilterResultSize="100" AutoFilterTimeoutMs="100"><AutoPostBackFlags ValueChanged ="Off"/><ClientEvents DropDownClosed="WebDropDown_DropDownClosed" /> </ig:WebDropDown>
Hi,
Could you try EnableAutoCompleteFirstMatch=false ?
Thanks,
Angel
In the latest service release, when there is checkbox multiple selection, and filtering, when you type "B", B1 will not only be selected, but also checked. That's the default behavior - when a match is found, the matched item is automatically selected. Currently it is still selected, but it is not visually correct (for which I completely agree with you), because the item doesn't appear as checked - though, it is still selected.
In the upcoming service release we plan to add a property that will allow the developer to cancel automatic selection when filtering is performed, i.e. AutoSelectOnMatch=false (something like that).
I will keep you informed when this is implemented in the control. Still, there is a workaround for this scenario - to disable automatic selection on filtering - using client-side events. I have presented the solution in the following forum thread: