We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

Problem with mdi main menu merging

Thread ID:





3277 Mar 11,2003 06:16 PM UTC Mar 14,2003 12:50 PM UTC WinForms 5
Tags: Tools
Don More
Asked On March 11, 2003 06:16 PM UTC

The merging doesn't seem to work, unless i use RegisterMdiChildTypes. My mdi child has a default ctor, but it setup the menus in code.

Administrator [Syncfusion]
Replied On March 11, 2003 06:46 PM UTC

Hi, Did you mean that you want merging to work without calling RegisterMdiChildTypes? That should work too. The mdi child constructor should initialize the menus. Make sure that you are following the rules for merging. The main-menus will be merged, the toolbars with the same name will be merged, etc. If possible, please attach a sample project here. Thanks Praveen Ramesh

Don More
Replied On March 12, 2003 04:51 AM UTC

The sample project work as exspected - but if I comment out RegisterMdiChildTypes in form.cs the merging fails.

Ramesh Praveen [Syncfusion]
Replied On March 13, 2003 06:50 PM UTC

Don, This is because you didn't call BeginInit/EndInit on the bar managers. Updating your BaseManager's Initialize like this fixes the problem: public void Initialize(Form form) { ((ISupportInitialize)m_barManager).BeginInit(); // Other stuff ((ISupportInitialize)m_barManager).EndInit(); } Regards, Praveen Ramesh

Don More
Replied On March 14, 2003 07:11 AM UTC

Thanks for the quick response. I really like your support. The interface is named ISupportInitialize and not IRequiredInitialize ;)...It seems like I have to enclose *some* MainFrameBarManager initialization with BeginInit/EndInit to make the merging work as expected. Can I just ignore ISupportInitialize, and stick to RegisterMdiChildTypes ? The Essential Suite is IMHO one of the best tools today, and like all other tools, it's very designer centric. While this is absolutely necessary, I think it often means that the 'none designer mode' is not as good as it could be. This tend to make designer centric tools less suitable for applications, which are 'highly plugable' with extension assemblies or macros. Does this make sense ? I could be wrong of course, but I seriously doubt it ;)

Ramesh Praveen [Syncfusion]
Replied On March 14, 2003 12:50 PM UTC

Don, You should be calling BeginInit/EndInit whether or not you use RegisterMdiChildTypes. It was our mandate to build the best designers for our componets, but the focus was defenitely not designer centric, which is why we store almost nothing in resource/xml files, etc. Regards, Praveen Ramesh


This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Please sign in to access our forum

This page will automatically be redirected to the sign-in page in 10 seconds.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon

Live Chat Icon For mobile
Live Chat Icon