How to tell when a window is moved? (MFC)

I am pretty new to Windows programming, but not to C++ in general. I am trying to figure out how, in my program, I would be able to tell when a window is moved; as in the user just clicking the title bar and dragging the window around. Is SetWindowPos called by the OS? I am trying to learn how to tell when this occurs and then get the window's new coordinates. I am trying to use this to then recalculate coordinates local to the application/program window. I have a 2D graphic element within the window that has it's own coordinates that I will be using, but I need to be able to tell if the window has moved to recalculate these coordinates in relation to the screen's pixel coordinates. Thank you for any help you might be able to give me.

You will receive a WM_MOVE message in your event loop.

--
Mats

Thank you Mats for the simple and concise answer. I appreciate it. I am however having a difficult time locating the event loop in this particular program. I am basically doing maintenance and bug fixing but have never had to mess with this sort of area of the code before. I was wondering if anyone would be able to tell me how I might be able to find it easier. I've been using VS' "find in files" option to search for various words or phrases that might lead me to the loop, but have been unable to find it thus far. Searched for things like DispatchMessage, Run, CWinApp, WindowProc (on the off chance they didn't give it a custom name). Any help would be greatly appreciated, thank you.

Yes, in MFC, you would probably do "onMove" or some such. Sorry, I missed that bit.

--
Mats

Thank you again Mats. I guess I should have been able to figure out from all the message maps that in MFC messages are handled differently on the surface, since it hides the details (I think). Thank you for all your help.

Moving a window is going to use a non-client area message since you must click on the title bar which is a non-client area in order to move it. Once you catch this message you can then do anything you want. I seem to remember that you must override the CWnd MsgProc in order to receive the message. There are certain Windows messages that do not get routed through MFC's normal message routing system and I believe this may be one of them.

I doubt it is, since this message is essential for many applications and blocking it from the message handler wouldn't be a wise thing to do by MFC.