[RESOLVED] PostQuitMessage: why the WM_DESTROY isn't called?

[Cambalinho]

heres my message loop:

WPARAM MessageLoop()
{
    MSG msgEvents;
    while(GetMessage(&msgEvents,NULL,0,0))
    {

        if(!IsDialogMessage(ActivatedForm,&msgEvents))
        {
            TranslateMessage(&msgEvents);
            DispatchMessage(&msgEvents);
        }
    }
    return msgEvents.wParam;
}

heres my End() function:

void End()
{
    if(hhookCBTProc!=0)
        UnhookWindowsHookEx(hhookCBTProc);
    PostQuitMessage(0);
}

why, when i use the PostQuitMessage(), the WM_DESTROY isn't called?
what window message i can use after the PostQuitMessage()?

[VictorN]

...
why, when i use the PostQuitMessage(), the WM_DESTROY isn't called?
what window message i can use after the PostQuitMessage()?

Because you are doing it the wrong way.
The correct way to close/exit the Windows GUI application is described in MSDN: https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

[Cambalinho]

i have 2 windows(forms).
1 call the End()(on menu click) and the other is the console window. but the WM_DESTROY isn't called, because, i belive, the message loop was closed.
so what you can tell me more?

[Cambalinho]

even the class destructor(any class) seems been ignored.

[VictorN]

...
so what you can tell me more?

Again, you must read the MSDN carefully to understand how to close windows application gracefully. I gave you a link in the post#2.

[VictorN]

even the class destructor(any class) seems been ignored.

It is because of the serious design and implementation bugs...

[2kaud]

when i use the PostQuitMessage(), the WM_DESTROY isn't called?

From MSDN
respond to WM_DESTROY by calling PostQuitMessage

As Victor has already explained, you call PostQuitMessage() from the WM_DESTROY message. PostQuitMessage doesn't generate a WM_DESTROY message. It indirectly terminates the message loop by posting a WM_QUIT message which when processed by the message loop will terminate the message loop.

even the class destructor(any class) seems been ignored.

A class destructor is called when a class instance goes out of scope. If a thread is 'terminated' - as opposed to being allowed to end gracefully, then destructors etc are not called. If you are finding that class destructors are not being called then you are not ending a thread correctly. Again, as both Victor and myself and stated, this is due to design issues.

[Cambalinho]

thank you to both. thanks for correct me