Current filter:
                                You should refresh the page.
                                Join us for the DevExpress WinForms Training Event
                                0
                                Michael Curry cl 06.14.2012

                                  • I have the same issue as in this ticket:


                                    http://www.devexpress.com/Support/Center/Question/Details/Q408412


                                    Which is very annoying to start with. I migrated to 12.1 based on the breaking change list for my latest app build and this item wasn't listed. All of my toolbars on child screens are now hidden I have to update around 50 forms.


                                    The problem is the new "feature" BarManager.HideBarsWhenMerging (which has no documentation) seems to have caused another issue in itself.


                                    I have toolbars in various locations on my child forms, not just as main menu bars, and I also have status bar on each child form, which I merge to the mdiparent.


                                    I want the toolbars left alone, and the status bar merged, but:


                                    With BarManager.HideBarsWhenMerging set to True, the status bar is merged by all of my toolbars are missing.


                                    With BarManager.HideBarsWhenMerging set to False, the status bar is merged but is still visible on the child form, so it shows twice.


                                    I need the old functionality back where I could merge the status bars and keep my toolbars visible. This is urgent as my app is currently in testing and this issue is holding up bug testing.

                                Show all comments
                                • Christophe Keller @ PTS 06.14.2012

                                  I just discovered the same behaviour in my applications too. This is annoying...

                                • Christophe Keller @ PTS 06.14.2012

                                  Well it seems to work if I set HideBarsWhenMerging to false on both the BarManagers from the parent and child forms. The should have set this new property to false by default to avoid an breaking change.

                                • Michael Curry cl 06.14.2012

                                  Good catch, I had set a Childbar.Visible = False in all my merge routines. Your way is much simpler, but I don't understand why it is necessary?

                                • Michael Curry cl 06.14.2012

                                  Actually I have just tried this approach, and it isn't working for me. I set both parent and child to HideBarsWhenMerging= False and I still get bars drawn in both parent and child.

                                • Uriah (DevExpress Support) 06.14.2012

                                  Thank you for your question. I am afraid that we do not have an immediate answer. I have passed this ticket to our team for further research. Please bear with us, we will get back to you as soon as possible.

                                • Uriah (DevExpress Support) 06.15.2012

                                  Christophe, thank you for your feedback. It appears we have overlooked the fact that in some scenarios the application design allows Bars to appear on the child MDI Form merged with the parent Form. When we were planning this feature, it was assumed that in common scenarios all Bars are merged in the BarManager.Merge event handler. Please accept our apologies for the inconvenience this change might have caused you. We will add a note about this issue into the Breaking Changes list.

                                • Scott G Blood 06.15.2012

                                  This caught me out as well, none of my MDIChildren with a ribbon on were merging the status bars correctly, really bad :(

                                • Conrad Akunga 07.12.2012

                                  Caught me up as well, and my project is pretty large with several forms.

                                  Does this mean everyone with DevExpress components going back several years will be caught out with this nasty bug?

                                • Stephen Winstanley_2 07.17.2012

                                  So the default is to break existing functionality, rather than let one request change a setting to suit what they need ? This seems very poor design DevExpress for one persons request. My application now has NO main bars or status bars on every child form (prior to any maximising so no merging has taken place).
                                  So I have to change every form to get back to 'default' behaviour. I think BarManager.HideBarsWhenMerging should be FALSE by default. More annoying madness.

                                • Michael Curry cl 07.17.2012

                                  I am still finding odd user controls on child forms with their own bar manager that suddenly lose all of their toolbars. Another was found by one of my users just now! Not good at all. I have spent probably 20-30 hours fixing toolbars and rewriting merge functions due to this change and it cost me countless hours with testers.

                                  I don't want to keep bitching about it but IMHO support has really dropped lately and this and other "by design" issues that keep cropping up now are really eating up my Dev time. My subscription is up for renewal next week and I am seriously considering whether it is worth it. Dx12.1, for winforms at least, introduced many more issues for me than new features. I'm not confident that I want to invest the time in getting 12.2 into my app.

                                • Uriah (DevExpress Support) 07.19.2012

                                  We are going to fix some problems caused by the new behavior. This will significantly decrease the drawback of the breaking change we introduced.
                                  Please check these bug reports:

                                  BarManager hides bars placed in StandaloneBarDockControl after merging
                                  BarManager should hide bars after merging only if the Merge event is handled

                                • Michael Curry cl 07.19.2012

                                  Thank you. This will certainly resolve the issues I am continuing to experience.

                                Show all comments
                                Leave a Comment
                                You must  log in  or  register  to leave comments

                                1 Solution

                                0
                                Uriah (DevExpress Support) 06.15.2012

                                Michael, I have tried your approach (hiding and making visible child bars manually), and it appears to work fine for me. I have attached a sample project demonstrating this. Would you please check whether or not we are doing this in the same way. If not, please modify my test project to reproduce the problem.

                                Q409061.ZIP
                                • Michael Curry cl 06.15.2012

                                  Thank you, my approach (and your example) does work, but Christophe's approach seemed to work for him, but does not work for me.

                                Leave a Comment
                                You must  log in  or  register  to leave comments
                                You must  log in  or  register  to leave an answer

                                Is your intention to post an answer to your own question?

                                • If so, then proceed.
                                • If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
                                • If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.