Learn more about custom messages!

A few days ago, I encountered a problem where debug was running normally and realese went wrong. After I wrote a blog, I felt I understood it all. Today, I still had a custom message in the project, but I had another error. We have done it again today and deepened our understanding of it.

This error is intended to respond to the itemchanged message of a clistctrl dynamically created by myself. After writing the message shadow, debug runs completely correctly. An error was found when I was running on realese at night. I didn't even think about it. It must have been a prototype error. In fact, the parameters in the prototype csdn are not very comprehensive. The simple method is also my solution to this problem. directly generate a project and put the desired control in a dialog box, then add the message response function to clsswizard. EditCode. Let's see his header file declaration. Haha. All the parameters are in. This method is the simplest and most straightforward.

Because all our message shadows are sent to the system for processing, the specific process is probably the message queue, and then to the framework .... The underlying functions of the system accept certain parameters by default. In the H file, you can define what you want to declare. So if you are not sure about custom messages, you can just create a project and generate a message response function directly on the control you want.