Re: Message 36? WM_????
From: CheckAbdoul (checkabdoul)
Date: 02/22/04
- Next message: Morten Aune Lyrstad: "Encrypting data with a password...?"
- Previous message: Alto: "Edit the autocomplate entries"
- In reply to: Bonj: "Re: Message 36? WM_????"
- Next in thread: .: "Re: Message 36? WM_????"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 22 Feb 2004 12:59:05 -0500
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" <a@b.com> wrote in message news:eDR7xpW%23DHA.3220@TK2MSFTNGP10.phx.gbl... > OK, it gets 36 (getminmaxinfo), 129 (wm_nccreate), then 131, then WM_CREATE > (which is 1). > What's 131? > > > > "Jeff Partch [MVP]" <jeffp@mvps.org> wrote in message > news:OGZjKeW%23DHA.3496@TK2MSFTNGP10.phx.gbl... > > "Bonj" <a@b.com> wrote in message > > news:OZRBLXW%23DHA.3820@TK2MSFTNGP09.phx.gbl... > > > 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%3Ben-us%3B67166 > > > > -- > > Jeff Partch [VC++ MVP] > > > > > >
- Next message: Morten Aune Lyrstad: "Encrypting data with a password...?"
- Previous message: Alto: "Edit the autocomplate entries"
- In reply to: Bonj: "Re: Message 36? WM_????"
- Next in thread: .: "Re: Message 36? WM_????"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|