🚀 go-pugleaf

"Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:
>It is technically possible to host MDI in a child form, but 
>you have to manage a few things manually.  Have a look at QC 
>#12006 for some details:
>
>http://qc.borland.com/wc/qcmain.aspx?d=12006

That looks promising. Thank you very much for the link Remy.

>> This is as well noticable when setting Left and Top after
>> SetParent - the child form gets drawn at another position!
>
>That is because you are setting the Left and Top properties 
>BEFORE calling SetParent(), so the property values are still 
>relative to the overall screen.  You should be calling 
>SetParent() immediately after instantiating the form and 
>before doing anything with coordinates.

Strange enough it is just the opposite. Calling SetParent after
setting Left and Top places the child form at the correct
position, whereas calling it beforehand kind of write-protects
the properties. I checked this in the debugger, Left and Top
keep their values, the assignments get ignored.

However, you have helped me a lot by showing that I can use MDI.
And there seems to be a solution without MDI, too. A collegue of
mine searched the web and found a solution by using the Parent
property and sending WM_NCACTIVATE to the child forms. Well,
this method has some drawbacks, like all child forms are kept activated for instance. The MDI solution seems better.

Thank you.