Exception from splitter control when no space is available

[Dongxian Li]

Hello,
I have a mdi windows application written in c# in VS Dot Net Framework 1.1.
It contains several dockable tools and a mdi childform. The childform contains a splitter control, on top of the splitter control is a GridControl.

The problem is when the application window is fully occupied by other tools and no space is left for the childform, openning the child form will give an exception. The source of the exception is the splitter control. The error message and call stack is shown below.
Is this a known issue or has been fixed in lastest version?

Our Syncfusion tool version is :
Essential Suite Version 2.1.0.9.
We would like to know how to avoid the problem from happening. Any suggestion would be appreciated.

Thanks
-Dongxian

Exception Message:bounds empty
Source: Syncfusion.Shared
Call Stack: at Syncfusion.Windows.Forms.SplitterControl.Refresh()
at Syncfusion.Windows.Forms.SplitterControl.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at Syncfusion.Windows.Forms.SplitterControl.WndProc(Message& msg)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.IntCreateWindowEx(Int32 dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x, Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu, HandleRef hInst, Object pvParam)
at System.Windows.Forms.UnsafeNativeMethods.CreateWindowEx(Int32 dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x, Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu, HandleRef hInst, Object pvParam)
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.IntCreateWindowEx(Int32 dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x, Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu, HandleRef hInst, Object pvParam)
at System.Windows.Forms.UnsafeNativeMethods.CreateWindowEx(Int32 dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x, Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu, HandleRef hInst, Object pvParam)
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Form.CreateHandle()
at System.Windows.Forms.Control.get_Handle()
at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
at System.Windows.Forms.Control.set_Visible(Boolean value)
at System.Windows.Forms.Control.Show()
at Teradyne.iStudio.DigitalTest.Tools.PatternSet.ShowPatternSet() in c:\userdatafolder\dwsrc\istudio\editors\digitaltest\tools\patternset\teradyne.istudio.digitaltest.tools.patternset\patternset.cs:line 1767

[Administrator]

Hi Dongxian,

no this is not a known problem and therefore also probably not fixed in the latest version.

The call stack itsself does not give any insight on my side what could be wrong.

Do you have a sample project that lets us reproduce and debug into the problem?

Thanks,
Stefan

[Dongxian Li]

Hi Stefan, I created a simple project that causes the exception. To reproduce the problem: Make the Textbox fully occupy the main window and click Open to open the child form. you get a bounds empty exception. If the textBox does not occupy the main window, the click open will open the childform without any problem. Please give us advice. Thanks -Dongxian >Hi Dongxian, > >no this is not a known problem and therefore also probably not fixed in the latest version. > >The call stack itsself does not give any insight on my side what could be wrong. > >Do you have a sample project that lets us reproduce and debug into the problem? > >Thanks, >Stefan > SplitterException2_4603.zip

[Administrator]

Thanks for that sample. We will remove that exception in our code. It is not needed. Stefan >Hi Stefan, > >I created a simple project that causes the exception. > >To reproduce the problem: >Make the Textbox fully occupy the main window >and click Open to open the child form. you get a >bounds empty exception. If the textBox does not occupy the main window, the click open will open the childform without any problem. > >Please give us advice. >Thanks >-Dongxian > > >>Hi Dongxian, >> >>no this is not a known problem and therefore also probably not fixed in the latest version. >> >>The call stack itsself does not give any insight on my side what could be wrong. >> >>Do you have a sample project that lets us reproduce and debug into the problem? >> >>Thanks, >>Stefan >> > >SplitterException2_4603.zip > >

[Dongxian Li]

So do you have a solution for us? Like provide us a patch? We are using Essential Suite version 2.1.0.9. Thanks -Dongxian >Thanks for that sample. We will remove that exception in our code. It is not needed. > >Stefan > >>Hi Stefan, >> >>I created a simple project that causes the exception. >> >>To reproduce the problem: >>Make the Textbox fully occupy the main window >>and click Open to open the child form. you get a >>bounds empty exception. If the textBox does not occupy the main window, the click open will open the childform without any problem. >> >>Please give us advice. >>Thanks >>-Dongxian >> >> >>>Hi Dongxian, >>> >>>no this is not a known problem and therefore also probably not fixed in the latest version. >>> >>>The call stack itsself does not give any insight on my side what could be wrong. >>> >>>Do you have a sample project that lets us reproduce and debug into the problem? >>> >>>Thanks, >>>Stefan >>> >> >>SplitterException2_4603.zip >> >>