Skip to main content

Que What is the use of CCmdTarget? Explain Command or Message routing with SDI & MDI applications?

his class is at the second level on MFC class inheritence hierarchy, derived direcly from CObject class. This class provides the Command routing or message routing through the different MFC framework classes.

Command routing or Message routing.

Windows event based model -- Let say an MFC application is running and user clicks on a menu item. Follwing sequence of steps are executed.

1. Any event (message) occured on any application running on window machine, is first received by windows operating system. Windows operating system retrives the thread running that application. OS send that message to message queue of the application for which it is created.

2. From own message queue application retrives the message and sends to the window of which handle is specifed..

This message is passed to the different classess for processing as follows.

In SDI Application

First sent to the Frame window class ( Derived from CFrameWnd). Frame window passes it to View class( Derived from CView or any view classes derived from CView). View class tries to handle it ( if handler is defined ), if not, passes to Document class ( Derived from CDocument). If document class is not able to handle it , passes it to fram class again. Frame class tries to handle it itself, if cant handle passes it to Application class( Derived from CWinApp). it application class is not able to handle it, it will be handled by Windows Default procedure.

in MDI Application

Similar to the SDI except it has saveral child frame windows, Views, documents. thus, before processed by main frame window all the DocTemplates tries to process it by roming through view, docs, child frames.

Comments

codediscuss said…
I'm sorry but I don't see the answer of your question of "What is the use of CCmdTarget?"
May 9, 2009 at 7:29 PM
sandy said…
Hi,

The above explained functionality of Windows Command / message routing is wrapped inside the class CCmdTarget. This is the class in MFC which is responsible for providing message and command handling.

If you derive a class from directly CObject that class will not have above functionality.
May 13, 2009 at 7:42 AM
Post a Comment

Popular posts from this blog

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

Function name mangling for C++ and Java

G++ internals - Mangling Both C++ and Jave provide overloaded function and methods, which are methods with the same types but different parameter lists. Selecting the correct version is done at compile time. Though the overloaded functions have the same name in the source code, they need to be translated into different assembler-level names, since typical assemblers and linkers cannot handle overloading. This process of encoding the parameter types with the method name into a unique name is called name mangling . The inverse process is called demangling . It is convenient that C++ and Java use compatible mangling schemes, since the makes life easier for tools such as gdb, and it eases integration between C++ and Java. Note there is also a standard "Jave Native Interface" (JNI) which implements a different calling convention, and uses a different mangling scheme. The JNI is a rather abstract ABI so Java can call methods written in C or C++; we are concerned he...
5 comments
Read more