Send WM_COMMAND

[heinduplessis]

I've done some searching through the forum but can't find exactly what I need - I might have it on it but I'm very new to AutoIt so I get confused easily

I just need to send a WM_COMMAND to a window handle and gui element ID.

The "traditional" winapi code is: PostMessage(h,WM_COMMAND, BN_CLICKED, id)

where h is the top level window handle and id is the id of the button I need clicked.

I'm sure it's just a few lines of code but for the life of me I can't hack it.

Many thanks.

[Skitty]

Use the sendmessage function

DllCall("user32.dll", "lresult", "SendMessage", "hwnd", $WindowHandle, "uint", $Windows_Message, "wparam", $wparam, "lparam", $lparam);0xFFFF = all windows

Edited July 2, 2012 by ApudAngelorum

[heinduplessis]

Use the sendmessage function

DllCall("user32.dll", "lresult", "SendMessage", "hwnd", $WindowHandle, "uint", $Windows_Message, "wparam", $wparam, "lparam", $lparam);0xFFFF = all windows

Thank you very much for your reply.

So, if I understand correctly, to replicate my sample above, I can send:

DllCall("user32.dll", "lresult", "SendMessage", "hwnd", 131816, "uint",273, "wparam", 0, "lparam", 4427);

131816 = Window Handle

273 = WM_COMMAND

0 = BN_CLICKED

4427 = ID of button

I've tried it but don't get the expected result, the button seems not to have clicked.

Is there something wrong with my implementation?

Edited July 2, 2012 by heinduplessis

[Skitty]

I just noticed that your attempting to use this to simulate clicking on a button.

Why not just use the controlclick command?

[BrewManNH]

Never hard code the window handle value into your script, it will change every time you run it.

[Zedna]

You can use _SendMessage() from standard include file Misc.au3

Here is similar use with WM_SYSCOMMAND

Edited July 2, 2012 by Zedna

[Zedna]

Never hard code the window handle value into your script, it will change every time you run it.

True. Instead use WinGetHandle()

[heinduplessis]

Thank you all very much.