Occasional "SplitterDistance must be between Panel1MinSize and Width - Panel2MinSize" exception kills FSI

[GoogleCodeExporter]

Occasionally we get the following exception message which kills FSI (possibly 
after calling FsEye.Show(), but hard to say, it doesn't happen very often):

System.InvalidOperationException: SplitterDistance must be between 
Panel1MinSize and Width - Panel2MinSize.
   at System.Windows.Forms.SplitContainer.set_SplitterDistance(Int32 value)
   at <StartupCode$FsEye>.$EyeSplitContainer.updateSplitterDistance@54(EyeSplitContainer this, Unit unitVar0)
   at <StartupCode$FsEye>[email protected](EventArgs _arg10)
   at Microsoft.FSharp.Control.CommonExtensions.SubscribeToObservable@2032.System-IObserver`1-OnNext(T value)
   at Microsoft.FSharp.Core.CompilerServices.RuntimeHelpers.h@749.Invoke(Object _arg1, TArgs args)
   at <StartupCode$FsEye>[email protected](Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnSizeChanged(EventArgs e)
   at System.Windows.Forms.Control.UpdateBounds(Int32 x, Int32 y, Int32 width, Int32 height, Int32 clientWidth, Int32 clientHeight)
   at System.Windows.Forms.Control.UpdateBounds()
   at System.Windows.Forms.Control.WmWindowPosChanged(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.SplitContainer.WndProc(Message& msg)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Stopped due to error

Original issue reported on code.google.com by [email protected] on 6 Jul 2013 at 6:33

[GoogleCodeExporter]

See discussion at 
http://social.msdn.microsoft.com/Forums/windows/en-US/ee6abc76-f35a-41a4-a1ff-5b
e942ae3425/splitcontainer-panel-minsize-defect, this appears to be a 
long-standing WinForms bug but we may be able to find a work-around.

Original comment by [email protected] on 6 Jul 2013 at 6:34

[GoogleCodeExporter]

Original comment by [email protected] on 21 Jul 2013 at 10:40

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

turns out this was not a VS bug after: was simple bug where this.Width was 0 on 
minimize, thus causing truly invalid splitter distance recalc.

Original comment by [email protected] on 8 Sep 2013 at 12:33

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by [email protected] on 10 Sep 2013 at 8:18

• Added labels: Milestone-Release2.0.1

[GoogleCodeExporter]

Im not sure if any body is going to respond. any how im facing the same problem 
and your answer seems to be the only positive one. But i still couldnt figure 
out which this.Width is 0 and how can i change it!!

Original comment by [email protected] on 30 Apr 2014 at 2:02