🚀 go-pugleaf

"Thorsten Kettner" <QUESTIONBYthorsten.kettner@otto.de> wrote:
>
>"Kent" <kentav@accessus.net> wrote:
>>Unless I'm missing something, when you maximize your window 
>>the title bar is not shown hence the child's title bar text is 
>>appended to that of the frame window.  So wouldn't your custom 
>>button need to be drawn on the title bar of the main window 
>>when the child is maximized?
>
>That makes sense. I am going to check it out. Thanx Kent.

My tests confirm it. I'm thinking that you'll have to duplicate
and implement the same code in the main form with some minor
changes to correctly calculate the placement of the button(s).

If you override the mdiChild's WndProc method and intercept
WM_SYSCOMMAND (testing WParam for SC_MINIMIZE, SC_MAXIMIZE
and SC_RESTORE), you can send a custom message to the main
form to activate or deactivate the code accordingly.

To correctly calculate the first button placement:

    TRect R;
    int NumberOfDefaultButtons = 3;
    R.top = ::GetSystemMetrics( SM_CYCAPTION ) + ::GetSystemMetrics( SM_CYFRAME );
    R.bottom = R.top + ::GetSystemMetrics( SM_CYMENU );
    R.right = Application->MainForm->Width - (::GetSystemMetrics(SM_CXFRAME) + (::GetSystemMetrics(SM_CXMENUSIZE) * NumberOfDefaultButtons));
    R.left = R.right - ::GetSystemMetrics( SM_CXMENUSIZE );

Note that the calculated TRect assumes a normal window with
left to right alignment.

~ JD