This message is sent to the dialog box procedure associated with a control. Normally, Windows handles all arrow-key and TAB-key input to the control. By responding to the WM_GETDLGCODE message, an application can take control of a particular type of input and process the input itself.
At a Glance
| Header file: | Winuser.h |
| Windows CE versions: | 1.0 and later |
Syntax
WM_GETDLGCODE wParam = 0; lParam = 0;
Parameters
pMsg
NULL if the system is performing a query, or is otherwise a pointer to an MSG structure.
Return Values
One or more of the values, indicating which type of input the application processes and described in the following table, is returned.
| Value | Description |
| DLGC_BUTTON | Button. |
| DLGC_DEFPUSHBUTTON | Default push button. |
| DLGC_HASSETSEL | EM_SETSEL messages. |
| DLGC_RADIOBUTTON | Radio button. |
| DLGC_STATIC | Static control. |
| DLGC_UNDEFPUSHBUTTON | Non-default push button. |
| DLGC_WANTALLKEYS | All keyboard input. |
| DLGC_WANTARROWS | Direction keys. |
| DLGC_WANTCHARS | WM_CHAR messages. |
| DLGC_WANTMESSAGE | All keyboard input (the application passes this message in the MSG structure to the control). |
| DLGC_WANTTAB | TAB key. |
Default Action
The DefWindowProc function returns zero.
Remarks
Although the DefWindowProc function always returns zero in response to the WM_GETDLGCODE message, the window procedure for the predefined control classes return a code appropriate for each class.
The WM_GETDLGCODE message and the returned values are useful only with user-defined dialog box controls or standard controls modified by subclassing.
See Also