can anybody help me out with my mouse problem? how do i detect mouse movement in my code?

i know that... but thanks. i already checked it actually, theres just so much, i was hoping for something a little more simple. like when you check for keyboard input, and mouse button input. i just want it to check for mouse movement. true or false type of thing.

sorry, yeah, i'm using windows messages to check for input. i'd like to use it for the mouse to, and i don't know much about directinput yet, but i would way rather use that for the mouse if its simple enough to set up

#define DIRECTINPUT_VERSION 0x0800
#include <dinput.h>

class TheMouse {

LPDIRECTINPUT8 pdi;
LPDIRECTINPUTDEVICE8 pmouse;

public:

TheMouse(HWND hwnd)
{
DirectInput8Create(GetModuleHandle(NULL), DIRECTINPUT_VERSION, IID_IDirectInput8, (LPVOID*)&pdi, NULL);

pdi->CreateDevice(GUID_SysMouse, &pmouse, NULL);
pmouse->SetDataFormat(&c_dfDIMouse);
pmouse->SetCooperativeLevel(hwnd, DISCL_FOREGROUND | DISCL_NONEXCLUSIVE);
pmouse->Acquire();
}

void getstate(int *dx, int *dy)
{
DIMOUSESTATE m_state;
pmouse->GetDeviceState(sizeof(DIMOUSESTATE), &m_state);
*dx = m_state.lX;
*dy = m_state.lY;
}

~TheMouse()
{
if (!pmouse) return;
pmouse->Unacquire();
pmouse->Release();
}


};


ok, to initialize, i need to call TheMouse::TheMouse(hwnd)
but to get the coords, i can't figure out how to get them out of the getstate. i know i need to do something with TheMouse::getstate(something, something) i think, can anybody help me pull out the coords from this?

You don't want to use DirectInput for mouse input. Please, just take my word for it. In fact this topic has been discussed here so many times I wish there were just a sticky I could link to.

At any rate...on WinXP and above all DirectInput does internally is register the mouse or keyboard as a Raw Input device and start a thread that reads WM_INPUT messages. This is kind of a waste, since a separate thread is really overkill for handling a few messages. If you want the high-precision mouse input that Raw Input affords you, you're better off just handling it yourself. The other benefit of handling it yourself is that you can also receive legacy WM_MOUSEMOVE messages, which is what you'll want to use for any GUI's you might have in your app (since these messages have pointer ballistics applied, which will make the cursor movement feel much more natural to the user).

As for the keyboard, there's really no reason to use Raw Input. With standard windows messages you'll retain support for alternate character maps and international keyboards, and you'll also retain normal usage of caps lock, shift, and key repeats.

Of course if you don't want to take my word for it, you can read what Microsoft has to say about it.

P.S. In case you didn't catch it, WM_MOUSEMOVE is the message you'll want to process for your situation. You'll receive one of those whenever the mouse moves inside your window's client area.