ASPxSplitter - A control with Width="100%" is displayed incorrectly inside a SplitterPane

Hello Claus,
Thank you for the project. I've reproduced the issue and forwarded it to our developers for a detailed examination. Sorry for a possible delay.
Thanks,
Vest

Hello Claus,
We've accepted this behavior as by design. A possible solution is available in our demo: ASPxSplitter - Controls Resizing. You should write code similar to the following one:

ASPx
<dx:ASPxSplitter ...>  
...  
<ClientSideEvents PaneResized="  
function(s, e) {  
  if(e.pane.name == 'gridContainerPane')  
    myGrid.SetWidth(e.pane.GetClientWidth());  
}">  
...  
</dx:ASPxSplitter>  

We won't embed this code into any of our controls for the following reason: the ASPxGridView can't change its width without any client-side calculations. It calculates its 100% width internally, by handling the WindowResize event. We can't embed the script above, because the web site layout might be complex and contain many grids, and it is impossible to calculate the width automatically.
Thanks,
Vest

Hey Vest,
thanks for your response.
But in my opinion, at the initial load of the page, a grid with width 100% should resize to fit its container pane size.
Moreover, at the initial load the pane.GetClientWidth() is 0. Otherwise I could add the following code to my grid (however this would only be a workaround IMO):
        <ClientSideEvents Init="function(s, e) {
            s.SetWidth(splMain.GetPaneByName('sppCnt').GetClientWidth()); }" />
But this doesn't work because GetClientWidth() returns 0.
Even if you put "alert(splMain.GetPaneByName('sppCnt').GetClientWidth());" in the onload event of the body tag, you will get 0 as result.
My splitter doesn't have resizing enabled; I just want it to have my menu on the top with the possiblity to hide it.
So how to get the grid to 100% before/without resizing a pane?
Well, you could use the client-side Init-Event of the ASPxSplitter Control. Curiously in that event pane.GetClientWidth() returns a value (while in body onload it doesn't?). But what do you do if the splitter is on a master page?
I managed to get it to work via putting the following code in the ASPxSplitter-Init on the master page:
function(s, e) {
    // use try, because on other child pages the grid doesn't exist…
    try {
        grdData.SetWidth(splMain.GetPaneByName('sppCnt').GetClientWidth());
    }
    catch (err) {
    }
}
But, if you have a project with let's say 20 different pages, 10 of them containing a grid, you'd have to code a huge try/catch statement on the master page.
So please re-think about your decision, maybe there is a better solution to it. I assume many customers won't understand why their grid ignores the setting width="100%".
Cheers,
Claus

PS: In your online demo "Controls Resizing", the gridview fully fills its container at the initial load, so it behaves like expected.
In my sample it doesn't - I guess it's because there is horizontal scrolling enabled.

Sorry for posting again, but - I apologize - I overread the following:
"We won't embed this code into any of our controls for the following reason: the ASPxGridView can't change its width without any client-side calculations. It calculates its 100% width internally, by handling the WindowResize event. We can't embed the script above, because the web site layout might be complex and contain many grids, and it is impossible to calculate the width automatically."
Okay, then it seems there is actually no better solution… thanks anyway!
Cheers,
Claus

Hi Claus,
We've changed our mind and will try to fix this issue.
As for our demo project, it works correctly due to the PaneResized handler. The splitter calculates its position when the page has been already loaded. The ASPxGridView and some other controls perform their layout before the splitter. As a result, their layout is incorrect at the moment when the splitter gets its final size. To work around this problem, we explicitly call PaneResized in our demo. You can use the same approach in your project.
Thanks,
Nick
--------------------
Check if Search Engine is able to answer questions faster than I do!