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.
Unfortunately, activation email could not send to your email. Please try again.

Merge Toolbars

Thread ID:

Created:

Updated:

Platform:

Replies:

5376 Jul 1,2003 06:34 AM Jul 29,2003 01:00 PM Windows Forms 24
loading
Tags: Tools
Peter
Asked On July 1, 2003 06:34 AM

I have an MDI application which uses XPMenus and has some MDI children. Now different MDI children merge some BarItems in the parent menu bar - all ok. But different MDI children have the same toolbar (all items are the same). But there appears a toolbar for every MDI child window. Is there a chance to merge a toolbar of one child window with a toolbar of another child window?

Peter
Replied On July 1, 2003 06:35 AM

Sorry I forgot: I'm using version 1.5.2.0

Ramesh Praveen [Syncfusion]
Replied On July 1, 2003 11:25 AM

For the different toolbars in the child forms to get merged, they should have the same BarName property and you should have called RegisterMdiChildTypes in your main Form's constructor (for example). If this still doesn't work please get our latest 1.6.1. Regards, Praveen

Peter
Replied On July 2, 2003 01:31 AM

Thanx, that works. But now I have some additional questions: 1. After "RegisterMdiChildTypes" there is an empty toolbar till the registered child form is shown. Is there a way to prevent that? 2. If I open a registered child form the toolbar disappears and reappears. That means there is a flickering in the toolbar which isn't very nice. Can I prevent this behaviour too? 3. I registered 2 child forms with the same toolbar (same name, same merge order, same items, same position of new groups). When the two bars are merged the position of the "new groups" is in disorder (means there are too many "new group" lines). How can that be fixed? TIA Peter

Ramesh Praveen [Syncfusion]
Replied On July 2, 2003 11:27 AM

Peter, I think you are not using our latest 1.6.1. Could you please redownload to get that. All your above issues should then get fixed. Regards, Praveen Ramesh

Peter
Replied On July 3, 2003 12:02 AM

Ok thanx

Peter
Replied On July 4, 2003 07:01 AM

Hi Praveen, I downloaded the version 1.6.1 and tried it out. Nearly all problems are gone and I have to tell you that there are very nice new features in that version. But I still have the problem that the item separators of the bars are in disorder. I have 2 forms with nearly identical bars. the first 10 items are identical and the second form has a 11th item. The separators a identical too but the second for has a separator before the last item. If I test the application the separators of the second form (the one with more items) are moved one item to the right. Can you help me?

Peter
Replied On July 7, 2003 11:47 PM

ping... Can you help me?

Ramesh Praveen [Syncfusion]
Replied On July 8, 2003 08:39 AM

Peter, It would be a big help if you could put togather a small sample that shows this problem. Once we can reproduce this we will be able to fix this in an upcoming patch. Thanks Praveen Ramesh

Peter
Replied On July 9, 2003 01:34 AM

Hi Praveen, attached is a sample which opens 2 forms (in the Window menu). The 2 forms do have the same bars and items but the second form has one more item and one more separator. The bars of the child forms are registered in the main form constructor. If you activate form 2 all is ok. If you activate form 1 you have the right items but a separator too much. Regards Peter

Ramesh Praveen [Syncfusion]
Replied On July 9, 2003 12:28 PM

Peter, Thanks for the sample. We can now reproduce the problem. We are working on a fix and the fix should be in our next patch release (in 10 days). We will notify you when the patch is ready. Thanks again for the sample and we apologize for the inconvenience. Regards, Praveen

Peter
Replied On July 9, 2003 11:35 PM

Thats fine, thanx Regards Peter

Peter
Replied On July 16, 2003 06:16 AM

I downloaded the latest patch and tried the behaviour of the separator indices if 2 bars are merged. The separators aren't merged together in the wrong order but now none of the separators are shown. Peter

Ramesh Praveen [Syncfusion]
Replied On July 16, 2003 02:52 PM

Peter, I have attached the screenshots (there was color loss when I saved it as gif, but u should be able to see the separators) of what I see in the new version (the expected behavior). This is by running the sample you had attached above. Maybe your persisted information is interfering with the logic. You could quickly test with the MainFrameBarManager's "Persistance" properties (3 properties you will see in the designer) turned off. You could also lose all your persisted information by going to your Isolated Storage and deleting it. This KB should give you more info: http://www.syncfusion.com/KB/Suite/Suite_c1c.asp#q540q Regards, Praveen Ramesh

Peter
Replied On July 17, 2003 09:16 AM

I cleared the isolated storage. It's a little bit confusing: I tested the sample and all works fine. In my application there is another behaviour: If I open one form all separators are shown. If I open another instance of the form all separators are shown. If I open another form (when the first form is shown) all separators are gone. If I merge some items with separators from the child mainmenu in the parent mainmenu none of the separators are merged.

Ramesh Praveen [Syncfusion]
Replied On July 17, 2003 02:32 PM

Peter, Could you please try to modify the sample to reproduce this issue? It's very difficult to put my finger on the issue without being able to reproduce it. Thanks Praveen

Peter
Replied On July 18, 2003 01:29 AM

Hi, now I can completely reproduce the behaviour. Look at the attached sample. You can open the subforms with MenuItem "Attribute" (Form2) in menu "Einrichtung" and MenuItem "Attributeklassen" (Form3) in menu "Einrichtung". If you open one instance of Form2 the separators are shown in the toolbar and items are merged to menu "Bearbeiten", but no separator is shown in the menu (it should appear bevore the merged item). If you open several instances of Form2 all is like described above. If you open one Form2 and one Form3 all is merged together correctly but no separators are shown. Peter

Ramesh Praveen [Syncfusion]
Replied On July 18, 2003 11:36 AM

Peter, Thanks for the sample. That was another minor bug. We have now fixed it. This should be in our next patch release. We will notify you pretty soon. To be sure, I suppose in your 2nd issue (no separators were shown after opening form2 and form3) you meant that there was no separator above the "TEST*" item? If so, that is fixed too. Regards, Praveen

Peter
Replied On July 18, 2003 11:44 AM

Hi, first of all I have to say that your support and bug - fixing is very fast and competently and - with some little exceptions (see my other entries and support calls) - your components are great. Now to your question: yes, I meant the separator above the TEST* items. Regards Peter

Ramesh Praveen [Syncfusion]
Replied On July 18, 2003 12:05 PM

Thanks for the nice feedback. We will try to get your pending issues resolved asap. Regards, Praveen

Peter
Replied On July 23, 2003 05:29 AM

This issue isn't fixed in the 1.6.1.4 version, is it? Peter

Peter
Replied On July 23, 2003 05:32 AM

Sorry, forgot something: If you don't "RegisterMDIChildTypes" the same error occours. If you register it works. Peter

Ramesh Praveen [Syncfusion]
Replied On July 28, 2003 01:47 PM

Peter, This does seem to work both when RegisterMdiChildTypes is called and not-called. I tested in the sample you had attached and saw that the "TEST*" item in the menu did have a separartor before it. Could you please double check? Please ensure that you are using 1.6.1.4 in fact. Thanks Praveen

Peter
Replied On July 29, 2003 07:54 AM

Hi, I checked it and the described behaviour occurs with the sample app. The version of the components is 1.6.1.4. Whenn the 1.6.1.4 version comes out I removed the old installation with 1.6.1.0 and installed 1.6.1.4. Can it be that the deinstallation/installation process isn't working probably? It's very confusing. Peter

Ramesh Praveen [Syncfusion]
Replied On July 29, 2003 01:00 PM

I think I spoke too soon :( I just figured that the fix didn't make it to 1.6.1.4. I apologize for the confusion. We were pretty close to code-freeze when the bug was discovered and I guess the fix barely missed the code-freeze. Anyway, our 1.6.1.5 which will be ready within a week will include the fix. I hope you can wait and sorry again for the inconvenience. Regards, Praveen

CONFIRMATION

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.

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.

;