WndProc (Mouse Input Hook) Problem

[Amrok]

Hi,

i've drawn a small square into wow via endscene hook.. Now i'd like to hook WoW's input event to determine if my rect was clicked and do nothing if it returned true.

I DONT WANT TO USE GLOBAL HOOKS.

Does sb. know how to do that? I think my Detour would look like

typedef LRESULT(WINAPI* MyWndProcType)(int,WPARAM,LPARAM);
MyWndProcType pWndProcHook = Detour(WndProcAddr, WndProcHook);

LRESULT WINAPI WndProcHook( int WndCode, WPARAM wParam, LPARAM lParam )
{
      // Check here

      return pWndProcHook( WndCode, wParam, lParam );
}

But i'm not sure how to set up (get the address of wndproc) in another process...

[swooshy]

You could do it completly without hooks eg: GetAsyncKeyState

[Amrok]

How would i stop wow from executing the click then?

[Cypher]

You could do it completly without hooks eg: GetAsyncKeyState

Yuck.

Anyway, getting the window procedure is pretty easy. From memory you can just get their D3D device then call the function to retrieve the parameters used to create the device. One of the members of that structure should be the window handle.

EDIT:

Here you go:
http://msdn.microsoft.com/en-us/library/windows/desktop/bb174382(v=vs.85).aspx

[Amrok]

Thank you! Okay now i've got access to the HWND.. GetMessage will do the job then. But HOW do i prevent the click then if my gui was clicked?

[Cypher]

Thank you! Okay now i've got access to the HWND.. GetMessage will do the job then. But HOW do i prevent the click then if my gui was clicked?

Just don't call your trampoline (i.e. WoW's original WndProc) and then obviously the input will never be passed to WoW. I'm pretty sure that will work.

Too lazy to pull up my old injected base code. I used SetWindowLongPtr though I think, I'm not sure whether you're doing that or using a detour, but I don't think it should make a difference anyway. (A detour is actually a lot easier because you don't have to worry about hook chains, but then that comes at the cost of having to modify WoW's .text section.)

[Amrok]

Just don't call your trampoline (i.e. WoW's original WndProc) and then obviously the input will never be passed to WoW. I'm pretty sure that will work.

I'm still not sure how u mean that...

For now i've only got the HWND of wow.

Example

HWND GetHWNDFromD3DDevice( LPDIRECT3DDEVICE9 pDevice )
{
	D3DDEVICE_CREATION_PARAMETERS pParams;
	pDevice->GetCreationParameters( &pParams );
	return pParams.hFocusWindow;
}

This function is called once in the EndScene Hook and the HWND is stored in my module.

Thats all i got for now.

EDIT: i'm dumb. Should totally L2R all the text b4 posting...

[Cypher]

Once you have the window handle you need to get the window procedure and then either subclass it, or detour it, depending which route you want to go. Both have their pros and cons. From there you can control whether input is passed down the chain or not.

[andy012345]

Just thought I'd hop in here since I have a hook for a different game that prevents clicks into it when over UI.

I detour it, if I want to give the click to the client, at the end I give it back to the original function, if not, you should call DefWindowProc.

Although my game uses a static address for the handler for procedures, so I can't help you with getting the pointer

[suicidity]

WNDPROC	g_gameWndProc;


{	// In your hook function
	g_gameWndProc = ( WNDPROC )SetWindowLongA( GAME_HWND, GWL_WNDPROC, ( LONG )WindowProc );
}

{	// In your unhook function
	SetWindowLongA( GAME_HWND, GWL_WNDPROC, ( LONG )g_gameWndProc );
}


LRESULT CALLBACK WindowProc( HWND hWnd, UINT Msg, WPARAM wParam, LPARAM lParam )
{
	tagMSG msg = { hWnd, Msg, wParam, lParam };


	if ( g_pInput->ProcessMessage( msg ) ) // This is my message handler
		return NULL;


	return CallWindowProc( g_gameWndProc, hWnd, Msg, wParam, lParam );
}

That's how I do it, hf.

[Cypher]

WNDPROC    g_gameWndProc;


{    // In your hook function
    g_gameWndProc = ( WNDPROC )SetWindowLongA( GAME_HWND, GWL_WNDPROC, ( LONG )WindowProc );
}

{    // In your unhook function
    SetWindowLongA( GAME_HWND, GWL_WNDPROC, ( LONG )g_gameWndProc );
}


LRESULT CALLBACK WindowProc( HWND hWnd, UINT Msg, WPARAM wParam, LPARAM lParam )
{
    tagMSG msg = { hWnd, Msg, wParam, lParam };


    if ( g_pInput->ProcessMessage( msg ) ) // This is my message handler
        return NULL;


    return CallWindowProc( g_gameWndProc, hWnd, Msg, wParam, lParam );
}

That's how I do it, hf.

Yep, that should work for most games.

Some games may require a bit of extra work (I seem to remember the UT3 engine calling SetWindowLongPtr and inserting itself on top of the hook chain for some stupid reason, so if you're injecting at process creation time you may need to also hook that API, but it's relatively easy to do).