Blank space at the bottom and no Minimum/MaximumSize when in tabbed view

180

Cristina Lopez Perera posted over 16 years ago

Hello.

I have a form that is Mdi container, and has an UltraTabbedMdiManager. Let’s call it MainForm.
MainForm has a Property called Tabbed that activates or deactivates the UltraTabbedMdiManager by changing the value of UltraTabbedMdiManager.MdiParent to this or null.
MdiChild (which inherits from Windows.Forms.Form) will be the base class of all the children that will be assigned to MainForm.
The implementation of MdiChild should include the assignment of the property MdiParent=MainForm.

My question is: where is the right place in the MdiChild implementation for assigning the MdiParent property? I tried assigning MdiParent in the constructor, before the InitializeComponent. Then I got this unwanted behaviors:

When I create a child having MainForm in Tabbed mode, a blank space appeared at the bottom.
When changing back from Tabbed to Normal, all the children created while in Tabbed lost the values of MaximumSize and MinimumSize.

Assinging MdiParent in the constructor, but after the InitializeComponent, results in the same behavior because the children are instances of inheritors of MdiChild, and their own InitializeComponent is being invoked after the base constructor.

Assigning the MdiParent in the OnLoad of the MdiChild will work, but it will force all the controls in the form to load twice.

44743

Mike Dour posted over 16 years ago in reply to Cristina Lopez Perera

Both the main menu issue and the loading issue sound like bugs. I would recommend submitting them to the support group: http://es.infragistics.com/gethelp.
Cancel
Reply

Cancel
180

Cristina Lopez Perera posted over 16 years ago in reply to Mike Dour
Hello Mike. Thanks for your response
About toggling between tabbed and non-tabbed: I followed your suggestion. I created and configured the UltraTabbedMdiManager in the constructor of the MainForm (just after the InitializeComponent), and set the UltraTabbedMdiManager.MdiParent to this. In the property Tabbed of the MainForm I’m Enabling/Disabling the UltraTabbedMdiManager. Here I have a new issue: As I want my MainForm to start in Non-tabbed mode, I have to disable the UltraTabbedMdiManager at the beginning. In the constructor of MainForm, just after assigning the UltraTabbedMdiManager.MdiParent to this, I’m setting UltraTabbedMdiManager.Enabled=false. When running the application, the MainMenu of the MainForm has disappeared. I solved this issue by setting UltraTabbedMdiManager.Enabled=false in the MainForm.OnLoad instead of at the end of the constructor. My question is: is this the way it is supposed to be?
About assigning the MdiChild.MdiParent=MainForm in the OnHandleCreated: your suggestion worked fine. I got the same effect than assigning the MdiParent from outside before invoking MdiChild.Show (but because of the way my application is designed, the MdiParent has to be assigned in the MdiChild implementation). However, I still got an issue there. Let’s follow these steps:

MainForm in non-tabbed mode

Create new MdiChild_1 and Show it (all the controls inside are loaded)

Change MdiForm to tabbed mode (all the controls inside MdiChild_1 are loaded again)

Create new MdiChild_2 and Show it (all the controls inside are loaded)

Change MdiForm to non-tabbed mode
As you can see, when an MdiChild form is created and showed being in non-tabbed mode, and then changed to tabbed, all the controls in the MdiChild form are loaded again (that happens only one time per form). This doesn’t happen when the MdiChild is created while on tabbed and then changed to non-tabbed. Is this the way it is supposed to be?
Cancel
Reply

Cancel
44743

Mike Dour posted over 16 years ago

First off, changing the value of the MdiParent on the UltraTabbedMdiManager from null to the Form or vice versa is not the proper way to toggle between tabbed and non-tabbed layouts. It is recommended that you instead set the Enabled property of the UltraTabbedMdiManager to True or False. Try changing this first to see if it fixes the issues.

If using the Enabled property still gives you the same issues, I would recommend trying to set the MdiParent after the entire Form's constructor has completed but before it has had its Handle created (due to a Show call). This would probably be easiest to accomplish from the code creating and showing the MdiChild, but if you must set the MdiParent from within the MdiChild, try overriding OnHandleCreated. In your implementation, set the MdiParent, then call the base implementation. It is after the handle is created, but it is the earliest sync point in the handle creation process and may prevent the loading of the form's controls twice.
Cancel
Reply

Cancel