I have a DropDownProvider for a WebDataGrid that is working as expected, but am not getting a postback when the selection has changed
The WebDataGrid is within an UpdatePanel
Also, I would like to know how to preselect the value matching the target (the dropdown list initially has nothting selected even though the cell has a value in the list. The second time the dropdown is selected (on a different row), it has the prevously selected value from the different row...)
Thank you!
<EditorProviders> <ig:DropDownProvider ID="StatusProvider"> <EditorControl ID="StatusEditor" runat="server" DisplayMode="DropDown" TextField="TaskStatusText" AutoPostBack="true"> </EditorControl> </ig:DropDownProvider> <ig:DropDownProvider ID="AssigneeProvider"> <EditorControl ID="AssigneeEditor" runat="server" DisplayMode="DropDown" TextField="ASSIGNEENAME" AutoPostBack="true"> </EditorControl> </ig:DropDownProvider> </EditorProviders>
Hi,
You will need to define an empty <ClientEvents /> tag For auto postback to work. Currently this is a known limitation. I guess you also have the server-side event handler already defined for SelectionChanged.
<ig:DropDownProvider ID="StatusProvider"> <EditorControl ID="StatusEditor" runat="server" DisplayMode="DropDown" TextField="TaskStatusText" AutoPostBack="true">
<ClientEvents /> </EditorControl> </ig:DropDownProvider>
Note that if you have auto postback for the dropdown when it is inside a grid, when the autopostback takes place, the grid value won't get updated this way. I suggest setting autopostback on the grid and using some of the grid events, like RowUpdating or ExitedEditMode.
I hope this helps,
Angel
Thanks for the help!
I am now getting the postback, but in additon am now getting an IE popup "Stop running this script"Really running slowThings aren't supposed to be this difficult!!!
I will try to redo the code to use auto postback on the grid
Terry
Hi Terry,
The "Stop running this script" warning could be related to various reasons. You can attach a sample project if posible, demonstrating the behavior, and i will take a look as soon as possible. You can also contact Infragistics Development Support for further in-depth investigation of the issue.
Thanks for the feedback,
I'm getting "Stop running this script" in several Infragistics controls, currently with the DropDown providerHowever, this only seems to be prevalent in IE8 - not occurring in FireFox 3.08 (if there is such a notification)(No longer have IE7 installed)
A fairly constent occurance is during page unload
Thanks Angel!You were spot-on that one. WebDataGrid rows were ok, I did have a DropDownProvider datasource with 1300 records in it - that one got away from me
Thank for pointing me in the right direction!
Thanks for the feedback. You can also try using the Paging behavior for the WebDataGrid. In order to determine whether the issue is in the dropdown itself, or in the WebDatagrid having too many records, one thing to also try is to isolate the WebDropDown out of the WebDataGrid, and bind it to the same number of records. If you still get the unresponsive script warning, this could be something in the dropdown going wrong. In general, the dropdown provider which allows the drpodown to appear as editor provider for a cell, keeps only one instance of the WebDropDown control, and only changes its location - not every cell has a WebDropDown instance created for it.
Another idea that pops to me is that there is a chance objects on the client-side are not properly disposed, if the unresponsive warning is reproduced after fair amount of user interaction with the grid.
For the WebDropDown, there are two features - EnablePaging=true , or EnableLoadOnDemand=true, which can help in scenarios where it is bound to many items ( i mean thousands).
Thanks again,
Wow - would love for you to eyeball this - however it is so far down in the code I'd end up spending a fair amount of time putting together a test harness/sample
I will decrease the number of rows in the WebDataGrid and see if that helps - presently at 200 rows/page
In general, this warning is observed in IE7 and IE8, when a fair amount of javascript code is executed and its duration is more than a couple of seconds. I suppose you may be loading too much data in the grid or dropdown. For such scenarios features like Paging or LoadOnDemand could certainly help for the dropdown itself (in general it has been tested with loading about 5 000 - 10 000 items at once ), but once it is in the grid, the scenario becomes a bit more complex.
I can take a look if you could attach some sample code / project.
Thanks very much for the input,