WinForm按钮WndProc中OnClick为何对应消息ID 0x2111而非WM_LBUTTONDOWN？

Great question—this is a super common gotcha when digging into how WinForms wraps the old-school Win32 API! Let's break this down step by step:

First, what is 0x2111 exactly? #

That magic number is actually a combination of two Win32 message constants:

• WM_REFLECT (0x2000): A special offset used by WinForms to "reflect" parent-targeted messages back to the control itself.
• WM_COMMAND (0x0111): The standard Win32 message used by controls to send notifications to their parent windows.

Adding them together gives 0x2000 + 0x0111 = 0x2111—the message you spotted in the Button.cs source.

Why not WM_LBUTTONDOWN? #

WM_LBUTTONDOWN (0x0201) is just a raw mouse input message—it only tells you the user pressed the left mouse button somewhere. A valid button click requires more: the user has to press the button inside the control's bounds and then release it there too.

The native Win32 button control handles all that validation internally. Instead of making you track down/up events and check bounds manually, it sends a BN_CLICKED notification (via WM_COMMAND) to its parent window only when a complete, valid click has occurred.

How WinForms brings this back to the Button control #

WinForms uses message reflection to let controls handle their own notifications, rather than forcing the parent form to manage everything. Here's the full flow:

1. User completes a valid click on the Button (presses and releases left mouse button within the button's bounds).
2. The native button sends a WM_COMMAND message to the parent Form, with the BN_CLICKED notification code stored in the high byte of the wParam parameter.
3. The Form's message loop catches this WM_COMMAND, recognizes it's a notification from a child control, and reflects it back to the Button by rewriting the message ID to 0x2111 (WM_REFLECT | WM_COMMAND).
4. The Button's WndProc method receives this 0x2111 message, checks that the notification code is BN_CLICKED, and then calls OnClick() to trigger the familiar Click event.

This way, WinForms leverages the native control's built-in logic for validating clicks, while keeping the event handling clean and encapsulated within the Button class itself.

内容的提问来源于stack exchange，提问作者Jack Zhang