Skip to main content

What is Message Maps ?

Message Maps


MFC uses message maps to get around a fundamental problem with virtual
functions. Look at the CWnd class in the MFC help file. It contains over 200
member functions, all of which would have to be virtual if message maps were
not used. Now look at all of the classes that subclass the CWnd class. For
example, go to the contents page of the MFC help file and look at the visual
object hierarchy. 30 or so classes in MFC use CWnd as their base class. This
set includes all of the visual controls such as buttons, static labels, and lists.
Now imagine that MFC used virtual functions, and you created an application
that contained 20 controls. Each of the 200 virtual functions in CWnd would
require its own virtual function table, and each instance of a control would
therefore have a set of 200 virtual function tables associated with it. The
program would have roughly 4,000 virtual function tables floating around in
memory, and this is a problem on machines that have memory limitations.
Because the vast majority of those tables are never used, they are unneeded.
Message maps duplicate the action of a virtual function table, but do so on an
on-demand basis.

When you create an entry in a message map, you are saying
to the system, "when you see the specified message, please call the specified
function." Only those functions that actually get overridden appear in the
message map, saving memory and CPU overhead.

When you declare a message map with DECLARE_MESSAGE_MAP and
BEGIN_MESSAGE_MAP, the system routes all messages through to your
message map. If your map handles a given message, then your function gets
called and the message stops there. However, if your message map does not
contain an entry for a message, then the system sends that message to the
class specified in the second parameter of BEGIN_MESSAGE_MAP.

That class may or may not handle it and the process repeats. Eventually, if no message
map handles a given message, the message arrives at a default handler that
eats it.
Labels:

Comments

Post a Comment

Popular posts from this blog

MFC - Microsoft Foundation Classes Design Patterns

1 Introduction This paper describes the use of object-oriented software design patterns, as presented in Design Patterns: Elements of Reusable Object-Oriented Software by Gamma et al., within the Microsoft Foundation Class Library (MFC). MFC is used for implementing applications for Microsoft Windows operating systems. Because of the size of the MFC library, a complete analysis would have been beyond the scope of this assignment. Instead, we identified various possible locations for design patterns, using the class hierachy diagram of MFC, and studied the source carefully at these locations. When we did not find a pattern where we expected one, we have documented it anyway, with examples of how the particular problem could have been solved differently, perhaps more elegantly, using design patterns. We have included a brief introduction to MFC in Section 2 , as background information. The analysis has been split into three parts, with one section for each major design pattern ca...
1 comment
Read more

Explain Polymorphism and Flavors of Polymorphism...

Polymorphism is the ability of different objects to react in an individual manner to the same message. This notion was imported from natural languages. For example, the verb "to close" means different things when applied to different objects. Closing a door, closing a bank account, or closing a program's window are all different actions; their exact meaning is determined by the object on which the action is performed. Most object-oriented languages implement polymorphism only in the form of virtual functions. But C++ has two more mechanisms of static (meaning: compile-time) polymorphism: Operator overloading. Applying the += operator to integers or string objects, for example, is interpreted by each of these objects in an individual manner. Obviously, the underlying implementation of += differs in every type. Yet, intuitively, we can predict what results are. Templates. A vector of integers, for example, reacts differently from a vector of string objects when it receives ...
17 comments
Read more

• Why might you need exception handling be used in the constructor when memory allocation is involved?

Your first reaction should be: "Never use memory allocation in the constructor." Create a separate initialization function to do the job. You cannot return from the constructor and this is the reason you may have to use exception handling mechanism to process the memory allocation errors. You should clean up whatever objects and memory allocations you have made prior to throwing the exception, but throwing an exception from constructor may be tricky, because memory has already been allocated and there is no simple way to clean up the memory within the constructor.
Post a Comment
Read more