Hi,
We use 8.3 version. One of our pages contains a number of grids. In this page, some of those grids suffer the problem, some do not.
The problem is composed of two parts:
1- The grid header normally should be at the top grid frame. However, the header comes to the middle of the frame.
2- The existing rows disappear.
The problem has an interesting solution -in fact, not a real solution-. If a postback is triggered somehow, the problem vanishes.
How can we fix the problem NOT using the fake, invalid solutions like above?
Thanks in advance...
Note:
1- We upgraded to 8.3 version a couple of days ago. Before that upgrade, our version was 8.2 and we didn't face the problem.
2- The page uses also UltraWebTab.
Hello,
Are you using StationaryMargins? If so, this seems like an issue that was reported recently and could be a bug - we need to investigate that. This seems very similar to what is reported here (hopefully some of the information there may help you alleviate the problem):
http://forums.infragistics.com/forums/p/16166/58874.aspx
In any case, please submit a support request, one for each individual issue you're encountering, so that a Developer Support Engineer can investigate them in more detail. If possible, please include a sample project that we can run and debug which reproduces the issue, since this will ensure that we're testing the same code you're using.
Hi again,
Thank for your reply, Rumen. The solution in the link you suggested has worked for my case. I removed StationaryMargins property and everything is OK. However, this solution has a side-effect for me. When the grid is scrolled, the header also is scrolled. That is a behaviour that we don't want. Without using StationarMargins="Header", is there an alternative solution to fix the header when scrolling rows?
Yes, I believe this was just a workaround, I am not sure that the side effects you get are acceptable in your sceanario. I believe the conclusion in the previous thread was to contact Developer Support directly (I've sent you a link in the previous forum thread) since I am not sure we can work this out here in the community forums and this might need special and dedicated attention from our support/development folks.