I can't figure out how to get the WebDropdown to autopostback ONLY when I have actually selected an item.
Using your own example shows the problem that I'm having. Please go to this page:
http://samples.infragistics.com/2009.1/WebFeatureBrowser/contents.aspx?showCode=True&t=WebDropDown/WebDropDownServerEvents.aspx~srcview.aspx?path=~srcview.aspx?path=WebDropDown/WebDropDownServerEvents.src
Now, click in the webDropDown, delete the text, and type just a 'B'. An autopostback happens, and says that I have selected "Berglunds snabbköp". Which is not the case - the webdropdown only has a 'B' in it.
I don't want a postback to happen until I either hit <enter> or click on a item. To further clarify my need, lets say that you actually wanted to select the second "B" item, which is "Blauer See Delikatessen". I want to be able to type "Bl" and not have a postback happen after the "B".
In my case, I'm setting EnableAutoFiltering="Client", which will filter the results. So, I want to be able to type a "B", and the result is filtered, BUT no postback happens yet, because I haven't selected anything yet. Then I type"L" (which filters, so "Blauer See Delikatessen", is now the first item - the item that I really want, so I now hit <enter>. This is when I want the autopostback to happen - because only now have I actually selected something. Up until now, I've only been typing.
Thanks,Jim
Hello Jim,
Let me know if you need further assistance.
It still doesn't work correctly. Here's my code: <form id="form1" runat="server"> <div> <asp:ScriptManager ID="ScriptManager1" runat="server"> </asp:ScriptManager> <ig:WebDropDown ID="WebDropDown1" runat="server" Width="200px" TextField="Prod_Code" ValueField="Prod_ID" AutoSelectOnMatch="false" EnableAutoFiltering="Client" OnSelectionChanged="WebDropDown1_SelectionChanged" DataSourceID="SqlDataSource1"> <AutoPostBackFlags SelectionChanged="On" ValueChanged="Off" /> </ig:WebDropDown> <asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$ ConnectionStrings:TravelerMakerGUIConnectionStringXXXX %>" SelectCommand="SELECT [Prod_Code], [Prod_ID] FROM [ProductCodes]"> </asp:SqlDataSource> </div> </form>The desired behavior is: A postback should only happen when:1) an item is selected with the mouse (this works)2) Only when the <enter> key is hit (not working) - postpacks also happen at other times.If the list is a bunch of part numbers like:abc-123abc-124abc-125def-123def-124Now, using my code and part numbers from above, select abc-124 with the mouse. a postback happens - this is correct.Now, pretend that you made a mistake, and you really wanted one of the def-123 parts. So, rather than use the mouse, you highlight the abc-123 item, and start typing 'D'..... A postback happens. I did not select a full partnumber, I just typed a 'D', and a postback happened. This postback should not happen, I did not select a part number. A postback should only happen if an item is selected with the mouse, or if I hit the <enter> key. Thanks, Jim
@jdresser,
I respect your opinion and I would like to keep a proper language in the community.
Thank you in advance!
Hi all,
I have investigated the issue, and I have asked our engineering staff to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 108257. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution. I will update you with any new information after the review.
Please let me know if you need more information.
Hello,
since I ran into the same problem but could not try the 12.1 release yet - is this fixed in 12.1?
By the way: Someone mentioned to set AutoSelectOnMatch="false" and first I thought this would solve the problem. But it does only if the WebDropDown has no selection. In this case it works as expected. If it has a selected item it shows the unexpected behaviour again.
Hi bernhardus,
According to the bug, this was verified in a build of 12.1 prior to shipping, so it should be in the RTM.
regards,
David Young
I have version 14.2 installed. Is this fixed. I am having same issue?