🚀 go-pugleaf

"Stefano Bonifazi" <stefboombastic@email.it> wrote in message
news:45919f15@newsgroups.borland.com...

> You mean that I have to create an hidden window with its WndProc
> callback function inside the console application calling the dll?

No.  A TForm already has a suitable window for processing messages.  You do
not need a separate hidden window at all.

The real problem is that console applications do no have any message queue
for receiving and dispatching the messages in the first place, so there is
nothing for the TForm to process.  That is what you have to implement
manually in your console code.  The simpliest message queue is one that
calls Peek/GetMessage(), TranslateMessage(), and DispatchMessage()
repeatedly for the lifetime of the process, or at least while the TForm is
active.  For example:

    #include <windows.h>

    BOOL CALLBACK HandlerRoutine(DWORD dwCtrlType)
    {
        PostQuitMessage(0);
        return TRUE;
    }

    int main(int argc, char** argv)
    {
        SetConsoleCtrlHandler(&HandlerRoutine, TRUE);

        // load DLL...
        // show TForm...

        MSG msg;
        while( GetMessage(&msg, NULL, 0, 0) > 0 )
        {
            TranslateMessage(&msg);
            DispatchMessage(&msg);

            switch( msg.message )
            {
                case WM_SYSCOMMAND:
                    if( (msg.wParam & 0xFFF0) != SC_CLOSE )
                        break;
                    // fall though to the next block...

                case WM_CLOSE:
                    if( PeekMessage(&msg, NULL, WM_QUIT, WM_QUIT,
PM_NOREMOVE) == 0 )
                        PostQuitMessage(0);
                    break;
            }
        }

        // close TForm...
        // unload DLL...

        SetConsoleCtrlHandler(&HandlerRoutine, FALSE);
        return 0;
    }


Gambit