Click here to Skip to main content
Click here to Skip to main content

Collapsible Splitter control in C#

By , 26 Aug 2003
 

Introduction

This control was modeled from the collapsible splitter used in the Mozilla web browser, but with some added functionality. This control allows a linked form control to be dynamically expanded and collapsed by clicking on the splitter control button, and resized by dragging the splitter. Additionally, there is an option to expanded or contract the parent form so that the control to expand doesn't take any further form area.

How it works

The CollapsibleSplitter derives from the System.Windows.Forms.Splitter class, working with 2 overrides, mouse event handlers, and exposing 4 new properties. The code is relatively straight-forward, and is well commented. The only code that I will cover here is the control painting and interaction with the base splitter control.

In creating the control, I first started by creating a new derived class with Stephen Toub's DeriveClass utility. The next step was to draw the control surface, first by finding the clip rectangle for the base splitter and then defining a new rectangle located in the vertical center of the splitter for the collapser control.

protected override void OnPaint(PaintEventArgs e)
{
    // force the width to 8px so that everything
    // always draws correctly
    this.Width = 8;

    // create a Graphics object
    Graphics g = e.Graphics;

    // find the rectangle for the splitter and paint it
    Rectangle r = this.ClientRectangle; // fixed in version 1.1
    g.FillRectangle(new SolidBrush(this.BackColor), r);

    // create a new rectangle in the vertical center 
    // of the splitter for our collapse control button
    rr = new Rectangle(r.X, (int) r.Y + ((r.Height - 115)/2),
        8, 115);

    // draw the background color for our control image
    if(hot)
        g.FillRectangle(new SolidBrush(hotColor), 
            new Rectangle(rr.X + 1, rr.Y, 6, 115));
    else
        g.FillRectangle(new SolidBrush(this.BackColor), 
            new Rectangle(rr.X + 1, rr.Y, 6, 115));

    // draw the top & bottom lines for our control image
    g.DrawLine(new Pen(SystemColors.ControlDark, 1), 
        rr.X + 1, rr.Y, rr.X + rr.Width - 2, rr.Y);
    g.DrawLine(new Pen(SystemColors.ControlDark, 1), 
        rr.X + 1, rr.Y + rr.Height, rr.X + rr.Width - 2, 
        rr.Y + rr.Height);

    // draw the arrows for our control image
    // the ArrowPointArray is a point array that 
    // defines an arrow shaped polygon
    g.FillPolygon(new SolidBrush(SystemColors.ControlDarkDark), 
        ArrowPointArray(rr.X + 2, rr.Y + 3));

    g.FillPolygon(new SolidBrush(SystemColors.ControlDarkDark), 
        ArrowPointArray(rr.X + 2, rr.Y + rr.Height - 9));

    // draw the dots for our control image using a loop
    int x = rr.X + 3;
    int y = rr.Y + 14;

    // Visual Styles added in version 1.1
    switch(visualStyle)
    {
    case VisualStyles.Mozilla:
        for(int i=0; i < 30; i++)
        {
            // light dot
            g.DrawLine(
                new Pen(SystemColors.ControlLightLight), 
                x, y + (i*3), x+1, y + 1 + (i*3));

            // dark dot
            g.DrawLine(
                new Pen(SystemColors.ControlDarkDark), 
                x+1, y + 1 + (i*3), x+2, y + 2 + (i*3));

            // overdraw the background color as we actually 
            // drew 2px diagonal lines, not just dots..
            if(hot)
                g.DrawLine(new Pen(hotColor), 
                    x+2, y + 1 + (i*3), x+2, y + 2 + (i*3));
            else
                g.DrawLine(new Pen(this.BackColor), 
                    x+2, y + 1 + (i*3), x+2, y + 2 + (i*3));
        }
        break;

    case VisualStyles.DoubleDots:
        for(int i=0; i < 30; i++)
        {
            // light dot
            g.DrawRectangle(
                new Pen(SystemColors.ControlLightLight), 
                x, y + 1 + (i*3), 1, 1 );

            // dark dot
            g.DrawRectangle(
                new Pen(SystemColors.ControlDark), 
                x - 1, y +(i*3), 1, 1 );

            i++;

            // light dot
            g.DrawRectangle(
                new Pen(SystemColors.ControlLightLight), 
                x + 2, y + 1 + (i*3), 1, 1 );

            // dark dot
            g.DrawRectangle(
                new Pen(SystemColors.ControlDark), 
                x + 1, y  + (i*3), 1, 1 );
        }
        break;

    case VisualStyles.Win9x:
        g.DrawLine(new Pen(SystemColors.ControlLightLight), 
            x, y, x + 2, y);
        g.DrawLine(new Pen(SystemColors.ControlLightLight), 
            x, y, x,y + 90);
        g.DrawLine(new Pen(SystemColors.ControlDark), 
            x + 2, y, x + 2, y + 90);
        g.DrawLine(new Pen(SystemColors.ControlDark), 
            x, y + 90, x + 2, y + 90);
        break;

    case VisualStyles.XP:
        for(int i=0; i < 18; i++)
        {
            // light dot
            g.DrawRectangle(
                new Pen(SystemColors.ControlLight), 
                x, y + (i*5), 2, 2 );

            // light light dot
            g.DrawRectangle(
                new Pen(SystemColors.ControlLightLight), 
                x + 1, y + 1 + (i*5), 1, 1 );

            // dark dark dot
            g.DrawRectangle(
                new Pen(SystemColors.ControlDarkDark), 
                x, y +(i*5), 1, 1 );

            // dark fill
            g.DrawLine(
                new Pen(SystemColors.ControlDark), 
                x, y + (i*5), x, y + (i*5) + 1);

            g.DrawLine(
                new Pen(SystemColors.ControlDark), 
                x, y + (i*5), x + 1, y + (i*5));
        }
        break;

    case VisualStyles.Lines:
        for(int i=0; i < 44; i++)
        {
            g.DrawLine(new Pen(SystemColors.ControlDark), 
                x, y + (i*2), x + 2, y + (i*2));
        }

        break;
    }

    // dispose the Graphics object
    g.Dispose();
}

The control rectangle is used in the MouseMove event to determine if the cursor is within the control area (hot), or in the base controls splitter area.  Once we know whether the cursor is in the 'hot' area we can change various aspects of the control:  use a highlighted background color, ignore or pass on the MouseDown event, and also set the appropriate mouse cursor.

// this method was updated in version 1.11 to fix 
// a flickering problem discovered by John O'Byrne
private void OnMouseMove(object sender, MouseEventArgs e)
{
    // check to see if the mouse cursor position is within 
    // the bounds of our control
    if(e.X >= rr.X && e.X <= rr.X + rr.Width && 
        e.Y >= rr.Y && e.Y <= rr.Y + rr.Height)
    {
        if(!hot)
        {
            hot = true;
            this.Cursor = Cursors.Hand;
            this.Refresh();
        }
    }
    else
    {
        if(hot)
        {
            hot = false;
            this.Refresh();
        }

        if(!controlToHide.Visible)
            this.Cursor = Cursors.Default;
        else
            this.Cursor = Cursors.VSplit;
    }
}

protected override void OnMouseDown(MouseEventArgs e)
{
    // if the hider control isn't hot, 
    // let the base resize action occur
    if(!hot && !collapsed)
        base.OnMouseDown(e);
}

Using the control

The CollapsibleSplitter control can be added to the toolbox using the pre-compiled dll in the demo application, or simply copy the class into your project and manually reference it in your code.

To Add the Collapsible Splitter to your VS.Net toolbox, follow these steps:

  • Right-click on the VS.Net Toolbox and select "Customize Toolbox..."
  • Select the ".Net Framework Components" tab, and click the "Browse.." button
  • Browse to and open the "CollapsibleSplitter.dll" file from the demo application archive
  • Click OK to add Collapsible Splitter control to your Toolbox.

Once you have it on a form, set the Dock property, and then set the ControlToHideproperty so that the splitter knows which form control to interact with. All properties specific to the collapsing behaviour can be found under the Collapsing Options group in the properties window. Once created on your form, the view state can be programmatically toggled by calling the ToggleState method, and the current state can be retrieved from the IsCollapsed property.

I hope you find this control useful, and if you improve this control, please email me the updated source. If you have any comments or suggestions, please post your thoughts in the feedback section below.

Updates

Version 1.1 Changes:

  • OnPaint is now overridden instead of being a handled event, and the entire splitter is now painted rather than just the collapser control
  • The splitter rectangle is now correctly defined
  • The Collapsed property was renamed to IsCollapsed, and the code changed so that no value needs to be set
  • New visual styles added: Win9x, XP, DoubleDots and Lines

Version 1.11 Changes:

  • The OnMouseMove event handler was updated to address a flickering issue discovered by John O'Byrne

Version 1.2 Changes:

  • Added support for Horizontal Splitters

Version 1.3 Changes: (24 Aug 2003)

  • Added an optional 3D border
  • General code and comment cleaning
  • Flagged assembly with the CLSCompliant attribute
  • Added a simple designer class to filter unwanted properties
  • Added support for inclusion as a VS.Net ToolBox control
  • Added a ToolBox bitmap
  • Removed extraneous overrides
  • Added summaries
  • Removed the ParentFolder from public properties - this is now set automatically in the OnHandleCreated event
  • Added expand/collapse animation code

License

This article, along with any associated source code and files, is licensed under The Microsoft Public License (Ms-PL)

About the Author

Furty
Web Developer
Thailand Thailand
Member
Furty will code for food.

Sign Up to vote   Poor Excellent
Add a reason or comment to your vote: x
Votes of 3 or less require a comment

Comments and Discussions

 
You must Sign In to use this message board.
Search this forum  
    Spacing  Noise  Layout  Per page   
GeneralRe: AnimationDelay does nothingmemberorientalCSharp20 Jun '10 - 21:49 
It should set "this.animationTimer.Interval = value;" in the Property of AnimationDelay
 
Thus it looks like follows:
 
[Bindable(true), Category("Collapsing Options"), DefaultValue("20"),
Description("The delay in millisenconds between animation steps")]
public int AnimationDelay
{
get { return this.animationDelay; }
set { this.animationDelay = value; this.animationTimer.Interval = value; }
}
GeneralNEWBEmemberLonnie117 Nov '06 - 9:04 
Can I use a button to do open/close the panels or do I have to use the toolbar? If I can use the button, how would I code it? This is my first time using c and I need all the help I can get.
 
Thanks
GeneralAccess Violation ExceptionmemberLouis-Philippe Carignan2 Nov '06 - 5:01 
Hi,
 
We have integrated the collapsible splitter into our application. It worked fine under .NET 1.1 but we now have issues with it under 2.0. The problem seems random as we can't find a pattern to reproduce it. It even happens when the form with the splitter in it is minimized. We sometimes get the following error message when the splitter paints itself.
 
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Drawing.SafeNativeMethods.Gdip.GdipDrawLineI(HandleRef graphics, HandleRef pen, Int32 x1, Int32 y1, Int32 x2, Int32 y2)
at System.Drawing.Graphics.DrawLine(Pen pen, Int32 x1, Int32 y1, Int32 x2, Int32 y2)
at CollapsibleSplitter.OnPaint(PaintEventArgs e) in C:\DEV\APTS\NJFLib.Controls\NJFLib.Controls.CollapsibleSplitter.cs:line 601
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run()
 
Any ideas on why this happen?
GeneralNice one dude !!memberscanner77716 Sep '06 - 21:48 
Big Grin | :-D
GeneralA problem used in MDI applicationmembergrrrrr14 Dec '05 - 13:32 
For example,I have a treeview docked in the left which is the hide control of the Collapsible Splitter control "CollapsibleSplitter1". Then it works well. But now I want to hide the ChildForm, and expand the threeview. How should I do?
GeneralI added an event &quot;StateChanged&quot; into the controlmemberWayne Wood13 Sep '05 - 4:28 
you know, sometimes we need to update other UI elements when the splitter folded or unfolded, but i found no event notification was raised when the state toggled in this control. then i added one by myself, which is very simple.
 
i'm fresh here, so i dont know how to post code or upload attachment package Frown | :( who can help me to post my modification? thanks
GeneralMemory problemmemberkanaan8118 Jul '05 - 4:09 
Hi
I think you have a problem in your code, because in the demo exe, every time we use your splitter in the exe the memory usage increase(you can monitor the memory usage with windows task manager) OMG | :OMG:
I think your allocate variables without deallocation..Roll eyes | :rolleyes:
 
kanaan

GeneralTabPagesmemberJon Lea17 Mar '05 - 11:21 
Furty - nice control and I have things working pretty much the way I want except that when I collapse your splitter to the right edge of a tabPage (this splitter hides panel4 docked to the right side) I no longer can see the splitter. I have a collapsible splitter on the left side (hidding panel1 docked to the left) and a splitter on the top (this hides panel2) and they work fine.
 
Any idea why the right side is giving me problems?
 
The app is a Form with a tabSheet and two tab pages. The second tab page is where the collapsible splitters are and the four panes:
 
panel2
panel1 VCS HCS VCS panel4
panel3
 
Thanks.
 
Jon.
GeneralRe: TabPagesmemberFurty17 Mar '05 - 16:13 
Hi Jon,
 
It sounds like you've got the second VCS as a child of Panel4, rather than a child of the TabPage itself. Failing this, it could be a z-order issue.
 
As noted in this[^] thread, all such issues usually end up being a simple heirarchy problem.
GeneralWorks fine on Form, buggy on ControlsussLee Grissom3 Mar '05 - 8:08 
When we put the splitter on a form, it works as expected. However, when we put it on a custom control (or standard panel), it has problems. It correctly draws itself, and correctly hides/shows the "controlToHide". However, the location of the splitter does not move. When we place everything on a Panel, it moves, but the "dark gray" outline of the "old" position remains. Our guess is that there is a bunch of extra processing that occurs behind the scenes on the Form vs. a control. Any ideas on how we might get this to work correctly? Thanks.

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Permalink | Advertise | Privacy | Mobile
Web02 | 2.6.130523.1 | Last Updated 27 Aug 2003
Article Copyright 2002 by Furty
Everything else Copyright © CodeProject, 1999-2013
Terms of Use
Layout: fixed | fluid