How to set width or height to RadSplitContainer wpf

Introduction

It is often a requirement when we use RadSplitContainer and we want to set width or height to RadSplitContainer. Here in this post we will see how to achieve this. When we use RadSplitContainer, we would like it to occupy a small space initially and if required we can drag it to take more space. This is normally achieved by setting the width for the control. If we are using two RadSplitContainer and if we wish to set these RadSplitContainer widths in 1:3 ratios, we may not be able to achieve this easily if you are not an expert in it. So here is a post to relieve your effort to achieve this.

If you can set the RadSplitContainer inside a Docking control, then we can set the width of each RadSplitContainer seperately. This is as shown below.

<telerik:RadDocking>
  <telerik:RadSplitContainer Width="300">
    <telerik:RadPaneGroup>
      <telerik:RadPane></telerik:RadPane>
    </telerik:RadPaneGroup>
  </telerik:RadSplitContainer>
  <telerik:RadSplitContainer>
      <telerik:RadPaneGroup>
        <telerik:RadPane></telerik:RadPane>   
      </telerik:RadPaneGroup>
  </telerik:RadSplitContainer>
</telerik:RadDocking>

If you try the above code, then the first RadSplitContainers will take a width of 300 and the other will take a width as required by its child controls. In most of the scenario we would like the second RadSplitContainers to take up the rest of the space. In order for the RadSplitContainers to take up the whole space you need to set the HasDocumentHost property of the Docking control to False. This is as shown below.

<telerik:RadDocking HasDocumentHost="False">
  <telerik:RadSplitContainer Width="300">
    <telerik:RadPaneGroup>
      <telerik:RadPane></telerik:RadPane>
    </telerik:RadPaneGroup>
  </telerik:RadSplitContainer>
  <telerik:RadSplitContainer>
    <telerik:RadPaneGroup>
      <telerik:RadPane></telerik:RadPane>   
    </telerik:RadPaneGroup>
  </telerik:RadSplitContainer>
</telerik:RadDocking>

Now the RadSplitContainer’s together will fill the rest of the space.

Parquet file experiments, findings and recommendations

Parquet is a binary file format designed with big data in mind where we must access data frequently and efficiently. The way it stores file on the disk is also different from other file formats. It is a column-based data file. And in reality it uses both row based and column based approach to bring the best of both worlds. The data is encoded on disk which ensures that the size remains small compared to actual data and is then compressed where the file is scanned as whole and cut out redundant parts. The query/read speed is dramatically fast when compared to other file formats. Nested data is handled efficiently which is quite cumbersome in other file format to achieve. Doesn’t require to parse the entire file to find data due to its way of storing data. This makes it efficient in reading data. Works quite efficiently with data processing frameworks. Automatically stores schema information. SQL querying is possible with this file format using Continue reading

Libish Varghese Jacob

Libish Varghese JacobI am currently working as a lead engineer in one of the leading wind turbine manufacturing firm. I have wide range of interests and getting my hands dirty in technology is one among them. I use this platform primarily as my knowledge base. I also use this platform to share my experience and experiments so that it might help someone who is walking the way I already did. The suggestions expressed here are the best to my knowledge at the time of writing and this may not necessarily be the best possible solution. I would pretty much appreciate if you could comment on it to bring into my notice on what could have been done better.