Visual C++/MFC Tutorial - Lesson 1: Behind the Scenes with Handles and Messages

Lesson 1: Behind the Scenes with Handles and Messages

Though you think you want to dive right into the code, you really don't. Windows programming is overwhelming at first. Let's take a quick look at how Windows works. The backbone of all of your programming will be responding to and sending messages. What are messages? Messages are simply a 32bit number designating some event. Example: You move the mouse, a message (defined as WM_MOUSEMOVE) is 'posted' to the active window. You press a key, a message (WM_KEYDOWN) is 'posted' to the active window. You resize the window, a message (WM_SIZE) is 'posted' to the active window. Get the picture?

Now where do these messages go? They get queued up and a window eventually takes them out of the queue and reacts to them. For instance when a window gets the WM_MOVE message it changes the coordinates of the window and redraws it on the screen.

Let's move on to Handles. Windows is very much object oriented. You have several window objects (like the desktop, the program your reading this with, etc...). How does the programmer distinguish all of these things in an non-object-oriented language? He uses handles.  Handles are a way to reference different windows objects. You can have handles to windows, handles to files, handles to allocated memory, handles to images, etc.  You can think of them as pointers. You must create them some how. And when you are done with them, you must destroy them. If you don't you will end up with what is called a resource leak. This could bring your system to a grinding halt. So take care to always make sure they are destroyed at sometime.

Now lets tie these two things together.  Say you have a window. You will have a handle to it (called an HWND). Lets name your handle your_HWND. The operating system wants to tell you to redraw your window because it was just uncovered by some other window. Windoze passes you a message like this:
PostMessage(your_HWND, WM_PAINT, 0,0);

This function posts a paint messages to the window with handle your_HWND. The last two parameters are used for extra information about the message. Don't worry about them for now.

Now your application will have a function with a big case statement in it to handle all of the messages. For example:

void  HandleTheMessage(long Message) 
  case WM_PAINT: 
  case WM_KEYDOWN: 


Ok that is basically how windows works under the hood. That should be enough to get you going when we start talking about MFC.


  • helpful for beginners

    Posted by tungnvn on 08/15/2006 02:54am

    Many learners want to code when reach new language.

  • thank you

    Posted by Legacy on 02/04/2004 12:00am

    Originally posted by: Anna

    i have read the whole windows socket programming documentation in the msdn and there was a lot of reference on the item MFC. i worked with PFCs before but you still enlightened me on in the simple explanations above. good job and keep on writing, you have a gift.

  • its wonderful !! but..

    Posted by Legacy on 11/15/2003 12:00am

    Originally posted by: sajeev

    its a good tutorial but it could have been more worthy if you could demonstrate it with some examples


    Posted by Legacy on 10/28/2003 12:00am

    Originally posted by: tapeshgoyal


  • could you please explain through example?

    Posted by Legacy on 09/04/2003 12:00am

    Originally posted by: sayali

    I have got whatever you wanted to explain but it would have been easier if i had some exe to show that actually.


    Posted by Legacy on 07/21/2003 12:00am

    Originally posted by: Hariprasad Ravikiran K

    I was just looking for such a tutorial to ship me safely and quickly from mid C++ to VC++ and MFC.
    Great Job !

  • nice

    Posted by Legacy on 06/29/2003 12:00am

    Originally posted by: eager mfc learner

    that was quite nice and helpful.

  • How nice you are!

    Posted by Legacy on 06/16/2003 12:00am

    Originally posted by: Michael

    I get more clear of handle and message processing via the tutorial. thanks very much!

  • No f#$" problem

    Posted by Legacy on 03/07/2003 12:00am

    Originally posted by: Johny Bravo

    it's ok.

  • none

    Posted by Legacy on 03/03/2003 12:00am

    Originally posted by: Adeel Ashraf

    It Was Simply Too Good For Me.

  • Loading, Please Wait ...

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Whether you're just now developing your first mobile app, refining an existing one, or deploying multiple apps, the process for doing so can be complicated. Utilizing a Rapid Mobile Application Development (RMAD) platform can help you not only make that process easier, but also help the business reach its goals in a timely, cost-efficient manner. This eBook outlines seven key factors to consider as you choose the right RMAD platform to meet your needs, and includes a quick-reference checklist.

  • Salesforce has been recognized by Gartner as a leader in this report for three years in a row. This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document. The Gartner document is available upon request from Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date