Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!mit-eddie!bloom-beacon!eru!hagbard!sunic!fuug!demos!relcom!jvdrd!kvitekp
From: kvitekp@jvd.msk.su (Pete Kvitek)
Newsgroups: comp.windows.ms.programmer
Subject: Faked WM_MOUSEMOVE while releasing mouse capture
Message-ID: <1990Dec26.060307.1097@jvd.msk.su>
Date: 26 Dec 90 06:03:07 GMT
Reply-To: kvitekp@jvd.msk.su (Pete Kvitek)
Organization: JV Dialogue, Moscow, USSR
Lines: 19


  Hi!
  While making some Set/ReleaseCapture() stuff, i noticed
  that ReleaseCapture() function generates faked
  WM_MOUSEMOVE message. It goes to the window underneath
  the mouse pointer at the moment of ReleaseCapture()
  call. This seems to be pretty reasonable since this
  window should be informed that pointer is now in it's
  area and all previous WM_MOUSEMOVE msgs were swallowed
  by the window captured the mouse input.

  Does anybody out there know if there are other
  situations when faked mouse move messages are
  generated? Maybe while hiding or moving windows ?

  > Pete
-- 
Pete I. Kvitek <kvitekp@jvd.msk.su>
Speaking from but not for JV Dialogue, Moscow, USSR