🚀 go-pugleaf

"JD" <nospam@nospam.com> wrote in message
news:3eab1440$1@newsgroups.borland.com...
>
> How did you remove the OldWindowProc? When I tried that the
> form never got displayed?
>

I just commented it out, I assumed that OldWindowProc is your code and of
course I did not write such a function on my test.


> >The function is called loads of times and
> >
> >HRGN hrgn = (HRGN) Message.WParam; returns :00000001
> >
> >when this happens DWORD dwCount = GetRegionData( hrgn, 0, NULL ); returns
0
> >and the main block doesn't run.
>
> Could you please be a bit more clear about what is what when?
>

I'll try;

I started a new app and dropped a label on it with it's caption set to
"label1".  I created a message map in the header and then dropped your code
snippet into the unit file.

ala;

(I've loaded a custom control since my last message and BCB4 is not working
now (Argh) so this is from your post and not the IDE but it is an accurate
reflection of what I did)

void __fastcall TForm1::NewWindowProc( TMessage& Message )
{
    //OldWindowProc( Message );    //<--- OldWindowProc is your code I
assume???????
    if( Message.Msg == WM_NCPAINT )
      {
          char *Buffer = NULL;       // <--- set breakpoint 1 here
          RGNDATA *pRgnData;
          HRGN hrgn = (HRGN) Message.WParam;
          DWORD dwCount = GetRegionData( hrgn, 0, NULL );

          if( dwCount > 0 )
            {
                Label1->Caption = "Made it to here";   //  <--- set
breakpoint 2 here
             // <snip>
            }
          if( Buffer ) delete Buffer;
      }
}

Often the app would break on BP1 even though nothing has covered the form's
border, when this is the case GetRegionData fails because hrgn is always at
00000001.

If I actually invalidated the form's border by moving it off screen, BP2
fires and now hrgn is at something like 0d0201030 (made this up but it is a
valid region handle).

So it works but I do not know why it receives so many WM_NCPAINT messages
that seem to be erroneous.

Hope this helps.

Chris