Docking Manager persist problem

[Christian Pogea]

i moved from syncfusion 2.0.5.1 to 3.0.1.0. now the embeded controls of a docking window won''t resize after the application is loaded. i use the "appstateserializer" as described in your knowledgebase. every time my application is started, i have to resize the mainwindow a little bit to resize all embedded controls in docking windows. how can i manually perform a resize of the embedded controls of a docking window? pic1.jpg is after the application is started and pic2.jpg is after i resize the mainwindow a little bit. bug2_7142.zip

[Administrator]

Hi Christian, There were a number of issues with DockingManager''s serialization in v3.0.1. Is it possible for you to upgrade to v3.2.1? Regarding your question, I think that SetControlSize might be what you''re looking for. Regards, Gregory Austin Syncfusion Inc.

[Christian Pogea]

i moved to syncfusion 3.2.1.0 and this behaviour is fixed. maybe it was a bug in 2.5.0.1

[Christian Pogea]

now i get an exception after closing the main window...

is it a known bug???

Informationen über das Aufrufen von JIT-Debuggen
finden Sie am Ende dieser Meldung, anstatt in diesem Dialogfeld.

************** Ausnametext **************
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
at Syncfusion.Windows.Forms.Tools.XPMenus.MdiClientNativeWnd.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.SendMessage(HandleRef hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.Control.SendMessage(Int32 msg, IntPtr wparam, Int32 lparam)
at System.Windows.Forms.Form.Select(Boolean directed, Boolean forward)
at System.Windows.Forms.Control.SelectNextControl(Control ctl, Boolean forward, Boolean tabStopOnly, Boolean nested, Boolean wrap)
at System.Windows.Forms.ContainerControl.AfterControlRemoved(Control control)
at System.Windows.Forms.Form.AfterControlRemoved(Control control)
at System.Windows.Forms.ControlCollection.Remove(Control value)
at System.Windows.Forms.ControlCollection.Remove(Control value)
at System.Windows.Forms.Control.Dispose(Boolean disposing)
at System.Windows.Forms.ContainerControl.Dispose(Boolean disposing)
at Syncfusion.Windows.Forms.Tools.DockHost.Dispose(Boolean bdisposing)
at System.ComponentModel.Component.Dispose()
at Syncfusion.Windows.Forms.Tools.DockHostController.Dispose(Boolean bdisposing)
at Syncfusion.Windows.Forms.Tools.DockControllerBase.Dispose()
at Syncfusion.Windows.Forms.Tools.SizingController.Dispose(Boolean bdisposing)
at Syncfusion.Windows.Forms.Tools.DockControllerBase.Dispose()
at Syncfusion.Windows.Forms.Tools.SizingController.Dispose(Boolean bdisposing)
at Syncfusion.Windows.Forms.Tools.DockControllerBase.Dispose()
at Syncfusion.Windows.Forms.Tools.SizingController.Dispose(Boolean bdisposing)
at Syncfusion.Windows.Forms.Tools.DockControllerBase.Dispose()
at Syncfusion.Windows.Forms.Tools.MainFormController.Dispose(Boolean bdisposing)
at Syncfusion.Windows.Forms.Tools.DockControllerBase.Dispose()
at Syncfusion.Windows.Forms.Tools.DockingManager.Dispose(Boolean bdisposing)
at System.ComponentModel.Component.Dispose()
at System.ComponentModel.Container.Dispose(Boolean disposing)
at System.ComponentModel.Container.Dispose()
at AMS.Form1.Dispose(Boolean disposing) in d:\dotnet\ams\form1.cs:line 336
at System.ComponentModel.Component.Dispose()
at System.Windows.Forms.Form.WmClose(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.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[Administrator]

Hi Christian, We are aware of this bug and it is in our system as Defect #245. The fix is currently in testing. If you want to be updated when it''s complete, please create a DirectTrac incident. Regards, Gregory Austin Syncfusion Inc,

[Christian Pogea]

does this mean, i have to update to a newer version, again??? i buyed the version 2.0 and all features i needed are there, but i have to update several times, because everytime there were major bugs. i am very frustrated.

[Administrator]

Hi Christian,

I''ve looked into this some more and it might be a different problem. Please try the following workaround:

private void Form_Closing(object sender, System.ComponentModel.CancelEventArgs e)
{
IEnumerator ienum = this.dockingManager1.Controls;
ArrayList dockedctrls = new ArrayList();

while(ienum.MoveNext())
dockedctrls.Add(ienum.Current);

foreach(Control ctrl in dockedctrls)
{
this .dockingManager1.SetEnableDocking(ctrl, false);
ctrl.Dispose();
}

this.dockingManager1.Dispose();

for (int i=0; i < this.mainFrameBarManager1.Bars.Count; ++i) {
this.mainFrameBarManager1.Bars[i].Dispose();
}

for (int i=0; i < this.mainFrameBarManager1.Items.Count; ++i) {
this.mainFrameBarManager1.Items[i].Dispose();
}

this.mainFrameBarManager1.Dispose();
this.Close();
}

Please let me know if this works.

Regards,
Gregory Austin
Syncfusion Inc.

[Christian Pogea]

it doesn''t work. i got this exception:

System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
at Syncfusion.Windows.Forms.Tools.XPMenus.MergedParentBarItem.Dispose(Boolean disposing)
at System.ComponentModel.Component.Dispose()
at Syncfusion.Windows.Forms.Tools.XPMenus.BarManager.Dispose(Boolean disposing)
at Syncfusion.Windows.Forms.Tools.XPMenus.MainFrameBarManager.Dispose(Boolean disposing)
at System.ComponentModel.Component.Dispose()
at AMS.Form1.Form1_Closing(Object sender, CancelEventArgs e) in d:\dotnet\ams\form1.cs:line 3746

[Administrator]

Hi Christian,

We''ve fixed that error in our internal patch. Could you please create a Direct-Trac incident and request v3.2.1.1?

Regards,
Gregory Austin
Syncfusion Inc.

[Christian Pogea]

i opened a direct trac incident, but didn''t get 3.2.1.1 and defect 245 is still not resolved.

i NEED URGENTLY an update. i consider to move back to 2.0.5.0, but there is a big issue with master detail griddataboundgrid with no workaround. is it possible to get a patch for this problem for syncfusion 2.0.5.0

thats the issue:
http://www.syncfusion.com/Support/Forums/message.aspx?MessageID=19632

[Administrator]

Hi Christian,

I have updated incident 18855 with the link to the patch.

Regards,
Gregory Austin
Syncfusion Inc.