//

// splitContainer2

//

this.splitContainer2.Dock = System.Windows.Forms.DockStyle.Fill;

this.splitContainer2.Location = new System.Drawing.Point(0, 0);

this.splitContainer2.Name = "splitContainer2";

//

// splitContainer2.Panel1

//

this.splitContainer2.Panel1.Controls.Add(this.chartGroup);

//

// splitContainer2.Panel2

//

this.splitContainer2.Panel2.Controls.Add(this.capacityGroup);

this.splitContainer2.Panel2MinSize = 243;

this.splitContainer2.Size = new System.Drawing.Size(560, 250);

this.splitContainer2.SplitterDistance = 311;

this.splitContainer2.TabIndex = 5;

Maybe it also needs to take into account the width of the splitter area. So maybe if the splitter area width is more than the 6 pixels different between the maximum and the value you are supplying then it fails.

Phil Wright
http://www.componentfactory.com
Free UI controls for .NET2

Hi,

Can you give me the exact repro steps. I.e. how are you adding the containers, what sizes are you setting them to, etc.

Thanks

Martin

Hi

n I am facing the same problem as above

i have created a horiztal splitcontainer with panel1 and Panel2. I used a splitcontainer in the panel2 which divided the panel2 horizontal. when trying to asign the minimum size property of the container2.panel2. i get the following error:

An error occurred creating the form. See Exception.InnerException for details. The error is: SplitterDistance must be between Panel1MinSize and Width - Panel2MinSize.

'SplitContainer2

'

Me.SplitContainer2.Dock = System.Windows.Forms.DockStyle.Fill

Me.SplitContainer2.FixedPanel = System.Windows.Forms.FixedPanel.Panel2

Me.SplitContainer2.IsSplitterFixed = True

Me.SplitContainer2.Location = New System.Drawing.Point(13, 0)

Me.SplitContainer2.Margin = New System.Windows.Forms.Padding(0)

Me.SplitContainer2.Name = "SplitContainer2"

'

'SplitContainer2.Panel1

'

Me.SplitContainer2.Panel1.Controls.Add(Me.SplitContainer3)

Me.SplitContainer2.Panel1.Padding = New System.Windows.Forms.Padding(0, 0, 3, 0)

'

'SplitContainer2.Panel2

'

Me.SplitContainer2.Panel2.Controls.Add(Me.GroupBox3)

Me.SplitContainer2.Panel2.Controls.Add(Me.Panel3)

Me.SplitContainer2.Size = New System.Drawing.Size(866, 538)

Me.SplitContainer2.SplitterDistance = 457

Me.SplitContainer2.SplitterWidth = 7

Me.SplitContainer2.TabIndex = 0

'

'SplitContainer3

'

Me.SplitContainer3.Dock = System.Windows.Forms.DockStyle.Fill

Me.SplitContainer3.FixedPanel = System.Windows.Forms.FixedPanel.Panel1

Me.SplitContainer3.Location = New System.Drawing.Point(0, 0)

Me.SplitContainer3.Margin = New System.Windows.Forms.Padding(0)

Me.SplitContainer3.Name = "SplitContainer3"

'

'SplitContainer3.Panel1

'

Me.SplitContainer3.Panel1.Controls.Add(Me.GroupBox1)

Me.SplitContainer3.Panel1.Controls.Add(Me.Panel1)

Me.SplitContainer3.Panel1MinSize = 0

'

'SplitContainer3.Panel2

'

Me.SplitContainer3.Panel2.Controls.Add(Me.GroupBox2)

Me.SplitContainer3.Panel2.Controls.Add(Me.Panel2)

Me.SplitContainer3.SplitterDistance = 150

Me.SplitContainer3.Panel2MinSize = 250

Me.SplitContainer3.Size = New System.Drawing.Size(454, 538)

Me.SplitContainer3.SplitterIncrement = 10

Me.SplitContainer3.SplitterWidth = 10

Me.SplitContainer3.TabIndex = 0

Thanks for the clear two choices. I hate UI design and I am glad that this solution could be found quickly! Again many thanks!

I don't think that MS are in the habit of hotfixing VS. You'll have to wait for the service pack, if there is one.

I must say in the strongest terms that this is long overdue, VS 2005 is considerably less stable than it's predecessor and contains a number of defects that are very detrimental to productivity, particularly with the C# WinForms designer. Although to be fair, we do use 3rd party UI components (ChartFX/DevX) and it is not clear whether the instability stems from them or the IDE. On the basis of other defects that are definitely not 3rd party, I know where I'd put my money.

I'd also like to thank the person who decided that the solution explorer should not synchronise with the currently active document as per 2003. This is a genuine pain in the rear.

My company is currently working on 2 projects: on in VB2003 and one in C#2005. While some of the new features in 2005 are spectacular (in particular the refactoring tools), based on my experience with it so far I would argue against any new projects or the migration of existing projects to 2005 until it is patched.

Put simply, it is still faster for us to develop in 2003, with the possible exception of medium to large scale refactoring. But as I understand, refactoring is not available in VB2005 anyways so......

p.s. apologies for the tangential rant but when you spend as muchmoney as I have on MSDN Univ. licenses I'm sure you'd feel the same.

Hey Martin, since you've figured out how to bypass the problem, how about you take all that rich knowledge and go impress the makers of the product by publishing a fix for it so we can download it?

Someone tell me why we're supposed to pay for this kind of tool with a somewhat psychotic behavior? I thought I did something wrong by golly, for a very long time (15 minutes to someone with ADD is an eternity). Can I bill MS for 15 wasted minutes and for the subsequent amount of time it requires for me to restrain the psychotic IDE from throwing crazy exceptions?

It is available andeven more visualized than cs refactoring unless you meant the built-in one.

VB2005 refactor url: http://www.devexpress.com/vbrefactor/

Ok, here is a quick workaround that I wrote. Simply use the control SplitContainerFix, provided below, in place of SplitContainer, and the problem should go away. It worked for me.

Use the code however you like, though I make no claims and take no responsibility for any harm that results (may cause tsunamis etc.)

Has this issue not been resolved by Service Pack 1?

I am trying to figure out how to include this class in my visual studio project (vb.net - the code has been converted) so all calls for resize to any one of 3 splitcontainers are called appropriately. Two below have vertical orientation and each is contained within the MainDisplay SplitContainer that has a horizontal orientation (actually the orientation changes depending on the way the underlying Panel is divided up. Thanks! -greg

SplitContainer_MainDisplay

SplitContainer_Panes_1_3

SplitContainer_Panes_2_4

This did it for me:

Left the Min Sizes in the designer as they where (150/2)and set them in the constructor.

public Constructor()

this.splitContainer1.Panel1MinSize = 350;

this.splitContainer1.Panel2MinSize = 200;

Ulrich

I avoid using SplitContainers and the other "new" container components for this very reason. It's much easier just to lay the panels and splitter out and set the docking properties yourself. Sure, it's an additional 20 seconds of buildout, but it saves you from all the headaches that are the result of dealing withpiddly bugs like this, not to mention the SplitContainer's unintuitive property set.

I'm actually working on a project right now and noticed it as well! I can't believe that MS is this bad at patching something that, to me, should be relatively simple.

All they need to do is change where it places the overall container code to before the panel code, correct?

Just out of curiosity, so I don't destroy my project, could someone please post an example of option 2 of what Martin Thorsen mentioned in his post... "Hook an event and set the min sizes there. Say the form's load event."

Thank you,

~ Kyle