🚀 go-pugleaf

Vladimir,

Thanks for the reply.   However, the WndProc() that I described was for a
custom component only.   It is not for a form, let alone the main form.   My
main form does not override the WndProc().

I only added the WM_QUERYENDSESSION message to the custom component's
WndProc as a test to see if that might be the problem.

A question about your code, though.   Do you really want to do the cleanup
in both the WM_QUERYENDSESSION and the WM_ENDSESSION?   Won't this result in
having your cleanup code execute twice?

Thanks again.
Joe

"Vladimir Stefanovic" <antivari@po.sbb.co.yu> wrote in message
news:437364bd@newsgroups.borland.com...
> > tried having this WndProc() trap the
> > WM_QUERYENDSESSION [...]
>
> Not only the WM_QUERYENDSESSION !
>
>
> This is the code that works fine for me:
>
> void __fastcall TDiMainForm::WndProc( TMessage &Message )
> {
>    switch ( Message.Msg )
>    {
>       // ... other messages ...
>
>       case   WM_QUERYENDSESSION:
>       case   WM_ENDSESSION:
>                 YourCleanUpCodeHere();
>                 break;
>
>       // ... other messages ...
>    }
>    TForm::WndProc( Msg );
> }
>
>
> -- 
> Best regards,
> Vladimir Stefanovic
>
>