title: Missing mouse movement messages in Win32
body: <p>I'm writing a Win32 OpenGL application for painting where it is critical that all mouse movement is handled. As it happens, sometimes the painting operation in my program is not able to perform in real time -- which is fine for me, as long as all mouse events are queued and can be handled later. Now I would have thought that this would simply be a matter of calling <code>PeekMessage</code> making sure to process all events, but when I do this, it is apparent that the mouse movements my application receives are not of the same fidelity that as those being displayed by Windows.</p>
  
  <p>Is this a feature of Windows? Are mouse event dropped when the application is labor intensive? Or am I missing something? In either case, what can I do to remedy this situation? I would like to avoid multi-threading, part of the reason being that, as I understand, Win32 requires the message callback to be in the main thread and I'm not sure about separating the OpenGL-stuff to a different context.</p>
  
  <p>And as for code example, I am essentially using the template code in the link below. The message I'm checking for is <code>WM_MOUSEMOVE</code>.</p>
  
  <p><a href="http://nehe.gamedev.net/tutorial/creating_an_opengl_window_(win32)/13001/" rel="nofollow">http://nehe.gamedev.net/tutorial/creating_an_opengl_window_(win32)/13001/</a></p>