Windows Message research
- List Of Windows Messages
- TREK HOW TO BUILD A VISUAL C++ DISPLAY TUTORIAL
- Libraries Documentation
- Messages and Commands
- Understanding the Message Loop
- Getting Started
- Handling Messages
- Solutions to Common Errors
- WM_LBUTTONDOWN message
- Module 1. Your First Windows Program
- Window Messages
- How to get the error message from the error code returned by GetLastError()?
- Module 2: Getting Started with Visual C++ 6.0 AppWizard 1
- Module 2: Getting Started with Visual C++ 6.0 AppWizard 2
- Module 3: Basic Event Handling, Mapping Modes, and a Scrolling View 1
- Module 3a: Basic Event Handling, Mapping Modes, and a Scrolling View 2
- Module 3b: Basic Event Handling, Mapping Modes, and a Scrolling View 3
- Module 4: The Graphics Device Interface (GDI), Colors, and Fonts 1
- Module 4: The Graphics Device Interface (GDI), Colors, and Fonts 2
- Module 4: The Graphics Device Interface (GDI), Colors, and Fonts 3
Complete Message Queue list to print out
complelte list and need to have a copy
a good demo from nasa.gov
Good examples to jump start
QUE book:Special Edition Using Visual C++ 6
Understanding Message Routing If there is one thing that sets Windows programming apart from other kinds of programming, it is messages. Most DOS programs, for example, relied on watching (sometimes called polling) possible sources of input like the keyboard or the mouse to await input from them. A program that wasn't polling the mouse would not react to mouse input. In contrast, everything that happens in a Windows program is mediated by messages. A message is a way for the operating system to tell an application that something has happened--for example, the user has typed, clicked, or moved the mouse, or the printer has become available. A window (and every screen element is a window) can also send a message to another window, and typically most windows react to messages by passing a slightly different message along to another window. MFC has made it much easier to deal with messages, but you must understand what is going on beneath the surface.
Messages are all referred to by their names, though the operating system uses integers to refer to them. An enormous list of #define statements connects names to numbers and lets Windows programmers talk about WM_PAINT or WM_SIZE or whatever message they need to talk about. (The WM stands for Window Message.) An excerpt from that list is shown in Listing 3.1.
Understanding the Message Loop Understanding the message loop and entire message sending structure of windows programs is essential in order to write anything but the most trivial programs. Now that we've tried out message handling a little, we should look a little deeper into the whole process, as things can get very confusing later on if you don't understand why things happen the way they do.
What is a Message? A message is an integer value. If you look up in your header files (which is good and common practice when investigating the workings of API's) you can find things like:
note: compile that small example as test.c under /Subsystem:Windows. otherwise it won't work!
If that doesn't work, your first step is to read whatever errors you get and if you don't understand them, look them up in the help or whatever documents accompany your compiler. Make sure you have specified a Win32 GUI (NOT "Console") project/makefile/target, whatever applies to your compiler. Unfortunately I can't help much with this part either, as errors and how to fix them vary from compiler to compiler (and person to person).
No comments:
Post a Comment