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?
Couple of ideas.
1) be sure you're databinding the grid in the "InitializeDataSource" event.
2) check and see if there's a hotfix available
3) rather than having the WARP do the paging for you, use the grid's asynch behavior. Set LoadOnDemand=xml, or from the designer check "enable ajax" in the smart tag list. There's also a sample on XML Paging in the feature browser.
Ok, so that was three ideas, but I'm not changing "couple" to "few" [:)]
-Tony
I think my issue may be related to this:
I have several controls (dropdownlist, buttons) outside of webgrid. I would like these controls trigger the grid to do thinks like go to different page, reload data. I also like this is an AJAX-like call: the button event handler can load the data and bind the data with the webgrid without refreshing the whole page.
Should I put the webgrid in a warp or put all these controls inside a warp?
Any examples?
Thanks,
Guangming
The warp should be able to access datavalues for any input controls on the form (not just the ones inside of the WARP panel). However, you can not set or update controls which are outside of the warp panel. I usually place my buttons inside the WARP or UpdatePanel just because it doesn't add a whole lot to the weight of the request/response, and it automatically gets hooked up (no need to add triggers).
To really understand what's going on, you'll probably need to step through your code and see what code path is being taken during an async call.