I have an ultrawebgrid inside a WARP with basic paging turned on. I'm able to change the page for the first time, but the second time, the page links become unresponsive. I have tried put into debugger and noticed that PageIndexChanged eventhandler is not even getting fired.
Anyone has any idea why?
Hello jeffwwong,
Did you find a solution to this issue?
I am facing the samme one for couple of days without any lack...
The first time i change the pager, it works fine, but then the links become inactive...
If i remove the warp, it works fine, but i need the warp functionality...
I tried several solutions like moving the code to Initialize_Databinding etc without any luck...
Anyone else outthere that can help me...i would appreciate it!
Hello,
It is really hard to figure out what is going on without seeing the code, I do have some suggestions though that may resolve/alleviate the issue
1) Use the built-in asp:UpdatePanel instead of WebAsyncRefreshPanel. WARP was originally designed before UpdatePanel was released and is intended primarily for ASP.NET 1.x backwards comatibility (where UpdatePanel is not available).
2) If you have anything related to the grid that is programmatic (e.g. with code), try moving it in different stages of the page lifecycle. For example if you are creating the grid dynamically, move it to the OnInit event of the page, etc
3) Try databinding the grid either declaratively (using declarative datasources) or using the InitializeDataSource event - this event gets fired whenever the grid needs datasource - for example for paging - and could be the better place to databind the grid.
HTH,
Following fixes this.
private
InitializeComponent()
{
(g1_PageIndexChanged);