🚀 go-pugleaf

PaoloItaly wrote:

>if i close all the window of my application "at hand", by clicking the X
>button, my child wndProc receive the wm_close, wm_destroy event.

That button sends 
 SC_CLOSE	Closes the window. This command sends a WM_CLOSE
message to the window. The window carries out any steps needed to
clean up and destroy itself.

That suggests that if you send yourself a WM_CLOSE, that it will have
the same effect as the X.
	case WM_COMMAND:	// message: command application menu
		switch(wParam)
		{
		case CM_EXIT:
			PostMessage(hWnd,WM_CLOSE, NULL,0);
			return 0;

>Closing my application from the main window (PostQuitMessage(0)) no event
>are sended at child windows.

PostQuitMessage is the _last_ thing you do.
It stops the message pump and exits.
Clean up everything _before_ posting that message.

>I've to take trace of opened windows myself and then call DestroyWindow, or
>there is a built-in Windows method to do this job ?

If sending yourself a WM_CLOSE doesn't do it, then you could try
sending an SC_CLOSE (See WM_SYSCOMMAND)

Something like
	DefWindowProc(hWnd,WM_SYSCOMMAND,SC_CLOSE, 0);