You need to be responding to WM_MOUSEMOVE messages really, either directly or through some kind of wrapper.

When you get WM_MOUSEMOVE first time, you need to store the mouse co-ords. When you get subsequent messages, you compare to the stored position and, if it is great enough (i.e. passed a threshold you define), close your program. If it is not, store the new co-ords and continue.

I handle WM_MOUSEMOVE and other Windows messages using the cracker macros in <windowsx.h> personally, as it saves having to mess about casting wParam and lParam.

HTH Paul

[EDIT] Actually, read the post below first before I start confusing you with message crackers. Probably not really needed in this case. [/EDIT]

Don't have any code to hand at the moment but basically WM_MOUSEMOVE is sent to your application's WndProc whenever the mouse moves. The parameters in the message contain the new X and Y position of the mouse as well as some other information about the state of the buttons etc.

<windowsx.h> crackers give you macros that you can use that take as parameters the message type and a pointer to a function to handle the message. The function pointer is set up with more meaningful parameters than examining a message directly.

If you look in <windowsx.h>, you can search and find the message you want to respond to, and a comment tells you the signature of the type of function you need.

WM_MOUSEMOVE looks a bit like this:

/* void Cls_OnMouseMove(HWND hwnd, int x, int y, UINT keyFlags) */
#define HANDLE_WM_MOUSEMOVE(hwnd, wParam, lParam, fn)

So you create a function with the same parameters as Cls_OnMouseMove in your code, then in your WndProc, inside your message switch, you do

HANDLE_WM_MOUSEMOVE(HWnd,wParam,lParam,MyMouseMoveFunction);

Where HWnd is your window handle and wParam and lParam are the parameters passed into the WndProc. The macro expands in such a way that wParam and lParam are automatically cast into the int x,int y and UINT keyFlags parameters, then your specified function is called with these parameters.

Your mouse-handling code could look a bit like:



So that until the mouse is moved by at least 10 pixels, the function will do nothing.

Sorry above code is not clear and probably full of errors but having to type it all from memory.

[Edited by - EasilyConfused on July 19, 2006 6:47:40 AM]

Not WM_MOUSEMOTION - WM_MOUSEMOVE.

This is a simple Windows message, so all you need to do is to handle it in your message loop. The parameters are not very difficult to understand:

switch (msg) {case WM_MOUSEMOVE:  { // I begin a block here because I want to create a POINT     // structure on the stack    if (wParam & MK_CONTROL) { } // control key is down    if (wParam & MK_SHIFT) { }   // shift key is down    if (wParam & MK_MBUTTON) { } // middle mouse button is down    if (wParam & MK_LBUTTON) { } // left mouse button is down    if (wParam & MK_RBUTTON) { } // right mouse button is down    POINT point;    point.x = lParam & 0x0000ffff; // low order word = x    point.y = lParam >> 16;        // high order word = y    // do what you want with the point structure  }  break;};

HTH,

When you go:

if(&NewLoc!=&OldLoc)

you are comparing the addresses of the tagPOINTS, not their contents. I'm not sure if you can != tagPOINTs directly. Probably not as I believe they are PODs. You may need to do

if((NewLoc.x!=OldLoc.x) || (NewLoc.y!=OldLoc.y))

or whatever their members are called.

With what you have posted above, the condition should always be true since the ADDRESS of the two tagPOINTs could never be the same.

Unless this was a typo when posting of course, in case what I have just said would be of no use at all [smile].

HTH Paul

You're welcome.

Quote:Original post by Servant of the Lord
P.S: What's the commands for hiding/revealing the mouse cursor as well? The one I found on MSDN I'm not using correctly, so if you can give an example of how to use that also, I would be grateful.

ShowCursor(TRUE) and ShowCursor(FALSE) always worked for me.