I need the grid to AutoPostBack on Column Resize as I am saving grid settings to persist them for the user's next visit. Post back for all other grid actions (column moved, column sorted, etc) works perfectly, however the postback on column resize causes the entire page to freeze. The mouse stays as a the four arrowed "move" pointer and nothing can be interacted with on the page. No errors occur in Visual Studio and the localhost webserver does not crash.
The grid is statically defined in the aspx page, however the column widths are not defined. Attempting to perform a column resize with autopostback disabled works perfectly. On postback from a different action, the column resized events fire as intended.
I am using Visual Studio 2010 and Infragistics 11.1. This error occurs in IE 9, FF 5, and Chrome 12.
Below is a picture of the grid when this occurs, the "column moving" vertical line persists after mouse up:
Hi bruestle2,
If you have not upgraded to the latest Service Release for 11.1, could you do so? That may fix the problem. If not, could you try to see if you can see if any java script exception is happening in the page?
regards,
David Young
When I installed 11.1 about five weeks ago I told it to automatically install updates, so it should have the latest, though I will double check tomorrow when I am able to access our account.
I used the debugger in IE9 and it gave me the following script error:
SCRIPT5009: 'draggingAction' is undefined
It referenced the following line of code from Infragistics:
var eventArgs = new $IG.ColumnResizedEventArgs([this,draggingAction.currentSourceColumn,draggingAction.currentColumnResizingGroup,draggingAction.currentColumnResizingGroupWidths,false,true]);
I don't know the name of this file, but it started with:
/************************************** IG.ColumnResizing ************************************/
Attached is a sample project that will reproduce the problem.
Thank you for the help!
This is a good catch. It is actually a bug in the source code. It has been submitted internally as 83840. It has been fixed and should be available in the next Service Release. That should be sometime in the middle of September. If you contact Developer Support, they can attach your case to the bug and you'll receive an e-mail when it ships.
-Dave