WM_SYSCOMMAND SC_MOVE eats up mouse events and mouse up is not fired?

Thanks for describing why you're doing this, because there's a much better approach: Return HTCAPTION in response to WM_NCHITTEST .

The DefWindowProc handler for WM_SYSCOMMAND will be eating the mouse button up message which is why you don't see it. However, your SendMessage call won't actually return until the drag has finished so you can take that as being notification of mouse button up.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.