Message 36? WM_????

  • Thread starter Thread starter Bonj
  • Start date Start date
B

Bonj

what is windows message 36? It seems to be getting fired to my wndproc even
before WM_CREATE.
 
Is it needed to be handled in a certain way, as it keeps firing before my
WM_CREATE message? A couple of others aswell actually, WM_CREATE is about
the fourth in the early stages of the newborn window's lifetime.
 
Bonj said:
Is it needed to be handled in a certain way, as it keeps firing before my
WM_CREATE message? A couple of others aswell actually, WM_CREATE is about
the fourth in the early stages of the newborn window's lifetime.

Like most messages, DefWindowProc will do what it believes to be the right
thing. If you don't want the default behavior, you can handle it. Here's a
kb article...

http://support.microsoft.com/default.aspx?scid=kb;en-us;67166
 
OK, it gets 36 (getminmaxinfo), 129 (wm_nccreate), then 131, then WM_CREATE
(which is 1).
What's 131?
 
Bonj said:
OK Thanks. Did you just know that off the top of your head?

Know which? I knew the message, knew the kb article was there, but did not
know the kb id or URL.
 
If you are debugging your application, type

messageNo, wm

in the watch window to get the actual name of the message. For example

131,wm = WM_NCCALCSIZE

--
Cheers
Check Abdoul [VC++ MVP]
-----------------------------------

Bonj said:
OK, it gets 36 (getminmaxinfo), 129 (wm_nccreate), then 131, then WM_CREATE
(which is 1).
What's 131?
 
Bonj said:
I use Borland

What Borland? Delphi? C++ Builder?

The windows.h comes with the platform SDK, and you need it, whichever
compiler you use, if you want to call the windowing API.

Arnaud
MVP - VC
 
Oh you've ATTACHED it! lovely! I'll just plug it in to the SDK include directory then shall I?
 
yes, Borland C++ builder. On my computer now
c:\borland\bcc55\includ
contains a huge amount of .h files. The normal amount for an include directory
When I install the SDK, th
c:\program files\microsoft.net\sdk\v1.1\includ
contains about 20 files

So I use Borland
 
Well what do you actualy GET with the .NET SDK then? Because you get the C#
compiler with the framework, and surely don't you need windows.h to compile
a managed C++ program?
 
Back
Top