🚀 go-pugleaf

Hi again.

I found only one part solution. I have noticed that when I maximize the MDI
child window the WM_SYSCOMMAND's of a child become WM_COMMANDS of the main
window. So I can do something like this inside the main window procedure:

switch (message){
    ...
    case WM_COMMAND:
        mdiActive = (HWND) SendMessage(mdi , WM_MDIGETACTIVE , 0 , 0);
        switch (LOWORD(wParam)){
        case IDM_TS_MDI_RESTORE:
        case SC_RESTORE:
             SendMessage(mdi, WM_MDIRESTORE , (WPARAM) mdiActive , 0);
             break;
        ....
}
return 0; //when processing WM_COMMAND application must return 0;
...

I have set MDI box procedure to leave WM_SYSCOMMAND for default processing.

The above proc. looks and works very nice. The child window restores itself
from maximized to restored position.
Unfortunately (for me) other commands (SC_MINIMIZE, SC_CLOSE) make the
application to crash.
(it ates all CPU resources and hangs).
It happens when I modify above proc. so it looks like this:

switch (message){
    ...
    case WM_COMMAND:
        mdiActive = (HWND) SendMessage(mdi , WM_MDIGETACTIVE , 0 , 0);
        switch (LOWORD(wParam)){
        case IDM_TS_MDI_RESTORE:
        case SC_RESTORE:
             SendMessage(mdi, WM_MDIRESTORE , (WPARAM) mdiActive , 0);
             break;
        case SC_MINIMIZE: //as a WM_COMMAND
            SendMessage(mdi, WM_SYSCOMMAND, (WPARAM) SC_MINIMIZE, 0);
            break;
        ....
 }
return 0;
...

Does anyone have a solution for that??
Thanks in advance.

PawelT