Skip to main content

Explain GetMessage(), PeekMessage(), SendMessage(), PostMessage().

These all functions are related to messages and application message queue.

Message - Windows programming is a event based programming. On occurring any event operating system notifies it to that specific application by placing event type message in that application's message queue. Further this message (event) is processed / handled by respective application.

Message Queue - This is queue associated with each windows application where messages
are posted for processing.

GetMessage() function waits for a message to be placed in the queue before returning.
This function continously seeks for message in a message queue.

PeekMessage() function does not wait for a message to be placed in the queue before returning. This is used to seek a specific message.


PostMessage() function places (posts) a message in the message queue associated with the thread that created the specified window and then returns without waiting for the thread to process the message.

SendMessage() function sends the specified message to a window or windows. The function calls the window procedure for the specified window and does not return until the window procedure has processed the message.
Labels:

Comments

Anonymous said…
Interesting. It would be nice to see examples of how this works. :-)
June 10, 2008 at 7:15 AM
Anonymous said…
Who knows where to download XRumer 5.0 Palladium?
Help, please. All recommend this program to effectively advertise on the Internet, this is the best program!
November 14, 2009 at 2:11 PM
Anonymous said…
clomid and birth defects | buy clomid no prescription uk - how much does clomid cost 2012, clomid metformin pcos success
November 14, 2012 at 9:09 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