Docking Manager Exception When Dragging

Hi,

Can you please help me understand why the follwing exception is sometimes thrown when using Docking Manager and then dragging a window. This does not happen frequently but sometimes (so it is hard to replicate). Is there a way to avoid this from happening?

Thanks for your help,
Mitul

System.ArgumentOutOfRangeException: Index 0 is out of range.
Parameter name: index
at System.Windows.Forms.Control.ControlCollection.get_Item(Int32 index)
at Syncfusion.Windows.Forms.Tools.WhidbeyDragProvider.GetMainFormController(Point ptscreen)
at Syncfusion.Windows.Forms.Tools.WhidbeyDragProvider.ProcessMouseMove(DockControllerBase controller, IDraggable ctrl, Point ptscreen)
at Syncfusion.Windows.Forms.Tools.DockHostController.HandleMouseMoveImp(MouseButtons button, Point pt)
at Syncfusion.Windows.Forms.Tools.DockHost.OnMouseMove(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseMove(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.Tools.DockHost.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)

Hi Mitul,

Thank you for using Syncfusion products.

Could you please send us a minimal sample illustrating the issue? Please try reproducing the issue in any of our shipped samples. It will be very helpful if you provide reproduce steps and more details about your application scenario in which case you have faced issue that would help us to track the issue and provide you the solution at the earliest.

Please let me know if any concerns.

Regards,
Fathima

I get a similar error with 6.2.0.40:

-------------------------------------
Exception type: NullReferenceException
Message: Object reference not set to an instance of an object.
[System.NullReferenceException]
Stack Trace:
at Syncfusion.Windows.Forms.Tools.DockingManager.DockToNewSizingController(DockStateControllerBase ctrl)
at Syncfusion.Windows.Forms.Tools.DockHostController.InvokeRegularDocking(DockStateControllerBase ddcbase)
at Syncfusion.Windows.Forms.Tools.DockHostController.InvokeDocking(DockControllerBase dc)
at Syncfusion.Windows.Forms.Tools.DockHostController.TransitFloatToDockInFloat()
at Syncfusion.Windows.Forms.Tools.DockHostController.ApplyDockInfo()
at Syncfusion.Windows.Forms.Tools.WhidbeyDragProvider.ProcessMouseUp(DockControllerBase controller, IDraggable ctrl, Point ptscreen)
at Syncfusion.Windows.Forms.Tools.DockHostController.HandleMouseUpImp(MouseButtons button, Point pt)
at Syncfusion.Windows.Forms.Tools.FloatingFormController.HandleMouseUpImp(MouseButtons button, Point ptclient)
at Syncfusion.Windows.Forms.Tools.FloatingForm.HandleMouseUp(MouseButtons button, Point ptscreen)
at Syncfusion.Windows.Forms.Tools.FloatingForm.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)
-------------------------------------

Actually there is not an "easy way" to replicate this, unfortunately this happens sometimes when simply playing around with the dockable controls.

Ampelio

Hi Ampelio,

Thank you for your patience.

We have sent this stack trace to our developers for more analysis. We will update you once we getback from them.

Please let me know if any concerns.

Regards,
Hema

Hi Ampelio,

Thank you for the patience.

Currently our developers are working on fixing this issue with high priority. I will get back to you with the time frame for this issue on or before Oct 10th, 2008.

Please let me know if any concerns.

Regards,
Hema

Hi Ampelio,

Currently our developers are working on fixing this issue with high priority. The fix for this issue is expected to be available on October 28th, 2008 and we will get back to you on same day with more details.

Please let us know if any concerns.

Regards,
Hema

Hi Hema,

we are actually clients of yours.
This bug is really annoying and occurs quite often, can you give me more information on this fix?

Since we have also bought the source code and at the moment we cannot switch to a new version, can we have the "diff" of the fix so that we can apply the patch to the Syncfusion library code?

Mant thanks in advance

Ampelio

>Hi Ampelio,

Currently our developers are working on fixing this issue with high priority. The fix for this issue is expected to be available on October 28th, 2008 and we will get back to you on same day with more details.

Please let us know if any concerns.

Regards,
Hema

Hi Ampelio,

Our apologies for the delay in getting back to you on this issue.

We have raised the priority of fixing this issue to maximum. We will try to fix this issue as soon as possible and and we will get back to you on or before November 24th, 2008. If the issue is fixed then We will anlysis the possibility to provide a patch in 6.2.0.40 version.

We assure you quick response in next 24 hours after you posting a queries in Direct trac, so always post your queries in Direct trac.

Please let me know if any concerns.

Regards,
Hema

Hi Ampelio,

We have investigated the issue with the information you have provided in this thread.we were unable to resolve the issue with the stack trace you have provided.If you still see this issue occurring we would like to investigate this issue again. Please provide a steps/video to reproduce the problem and we will re-investigate.

Regards,
Poly