This is probably not about the WHDG really but im hoping for some inspiration.
I have a reasonable complex page, its a web content form but there isnt much on the master page, mainly for the menu and a few other little things like a message area.
On the content form I have one update panel for header information which contains a few text fields and some date pickers etc. Underneath this are two WHDG's located each in its own td in a table row for positioning.
In the header update panel I have some buttons like save and edit etc for the header info. The problem I am having is that it seems to take anything from 2-8 seconds to start postback when I first load the page if I dont expand the grids it happens in about 2 seconds, once the grids are all expaned this increases to 8 or more seconds before the screen grays out etc. Once the postback starts its all over in about a second and a half.
I knows its difficult without the code, but there is simply too much linked stuff to post a working copy. I was hoping someone might have some inspiration. I have tried to isolate the issue but bar removing almost everything nothing seems to make a difference.
Cheers
Hi Tsvetlina,
I have created a case for this now because I have done quite a lot of research. I also posted a solution which demonstrates with the case.
Chrome does not exibit this problem, but Both 7 and 8 versions of IE do. Please take a look at my case and read my introduction as there is important information in it.
Regards -- Terry ( PS, hope you had a nice Christmas. )
Hello Soberly,
At the beginning I started to search the cause of the issue in the WebHierarchicalDataGrid:
1) InitialDataBindDepth = -1
http://forums.infragistics.com/forums/p/47523/254027.aspx
2) Growing ViewState on post back ( issue in WebDataGrid : fixed and available in the next service release)
http://forums.infragistics.com/forums/p/49694/263443.aspx
After your second post I started wondering if it could be browser issue.
Does the delay occurs with IE8?
Good try.
321K Expanded or Unexpanded
Good try, but the grids area already bound at the lowest level and the "Apparent" page size does not increase when the grids are expanded. The rendered page sizes are of course the same as no postback occur at expansion.
The other thing I have noticed is that repeated postbacks via the buttons even when they dont have code behind them eventually result in a slightly longer delay before postback acuallly occurs.
I tried this with Firefox and Chrome and it doesent happen. Odd Right ?!? I reloaded version seven of IE and ran the malware as well, no change.
Hi,
I'll give a shot at inspiration:)
I would bet that your page size is really big. When you expand the WHDG, all that data is now on your page and the postback will be even bigger. When you have the page open right click and save the source of the page to a file. Compare the sizes when the grid is expanded and not.
I wonder if your WHDG has tons of records and you don't have paging enabled. That would be a way to have gigantic page sizes without noticing it.
Ed