joe_pool_is
Contributor
In my Mdi Form with more than one Mdi Child open:
If the active, Maximized form is disabled during a lengthy call, it is sent to the back. If I then bring the form back to the front after the call (BringToFront), the child form's WindowState is no longer Maximized.
Is this a bug, or is this by design?
I would typically set a form's Enabled state to false while making any SQL call, then reset it to true afterwards. This technique looks and works nice; also, our employees have no problems using it.
Now that I have moved the form into an Mdi Container, I get these issues.
Should I simply not disable a form if it is an Mdi Child in an Mdi Container?
If the active, Maximized form is disabled during a lengthy call, it is sent to the back. If I then bring the form back to the front after the call (BringToFront), the child form's WindowState is no longer Maximized.
Is this a bug, or is this by design?
I would typically set a form's Enabled state to false while making any SQL call, then reset it to true afterwards. This technique looks and works nice; also, our employees have no problems using it.
Now that I have moved the form into an Mdi Container, I get these issues.
Should I simply not disable a form if it is an Mdi Child in an Mdi Container?