CODEWITHSUNDEEP
c++apiwinapi
oks5
oks5

Reputation: 23

C++ Win32 API Controls messages

im starting with Win32 api, im adding a button control to my main window with the flowing code:


 HWND boton = CreateWindow(
    "BUTTON",   //
    "Caption",       // 
    WS_TABSTOP | WS_VISIBLE | WS_CHILD | BS_DEFPUSHBUTTON,  // Styles.
    250,         // x position.
    10,         // y position.
    100,        // Button width.
    40,        // Button height.
    hwnd,       // Parent window.
    NULL,       // No menu.
    (HINSTANCE)GetWindowLong(hwnd, GWL_HINSTANCE),
    NULL);      // Pointer not needed.

how can i assign it an id, so i can get the message on the loop, in the message loop im trying to catch the message as WM_COMMAND but i don't get any result i've tried with WM_NOTIFY too.

Upvotes: 2

Views: 2937

Answers (3)

dreamlax
dreamlax

Reputation: 95335

To assign it an ID, you have to use the hMenu parameter. If you have specified that the window will be a child (i.e. with WS_CHILD), the hMenu parameter will be interpreted as an integer ID for the window. Also, provide the BS_NOTIFY style.


HWND boton = CreateWindow (
    "BUTTON", 
    WS_TAPSTOP | WS_VISIBLE | WS_CHILD | BS_DEFPUSHBUTTON | BS_NOTIFY,
    250, 10, 100, 40,
    hwnd,
    (HMENU)101,  // This becomes the Control ID
    (HINSTNACE)GetWindowLong(hwnd,GWL_HINSTANCE),
    NULL);

EDIT: Special shout goes out to Heath Hunnicutt for the info on BS_NOTIFY.

Upvotes: 2

Heath Hunnicutt
Heath Hunnicutt

Reputation: 19457

In fact, you do not need to specify an ID for the button. The problem is your code is missing a style bit to CreateWindow().

You must specify the style BS_NOTIFY for the parent window to receive notifications from Button controls.

You will then receive window message WM_COMMAND with (HIWORD(w_param) == BN_CLICKED) every time your button is clicked. See the BN_CLICKED documentation for more.

Using a control ID is unnecessary because the BN_CLICKED message will provide you with the control's window handle. Because you are already required to keep track of the window handle in order to properly call DestroyWindow when you receive WM_DESTROY comparing the button's window handle is just as easy as using a control ID.

Upvotes: 2

Jeff Paquette
Jeff Paquette

Reputation: 7127

To set the window id, pass it in as if it were an HMENU:

(HMENU) nChildID

Upvotes: 0

Related Questions