No need to handle WM_CANCELMODE, defwindowproc takes care of it
(releasing capture), and we have WM_CAPTURECHANGED to make sure our application is in consistent state git-svn-id: https://svn.code.sf.net/p/freeglut/code/trunk@1528 7f0cb862-5218-0410-a997-914c9d46530a
This commit is contained in:
parent
c0522d1fcf
commit
ccebf6f3df
@ -624,17 +624,6 @@ LRESULT CALLBACK fgPlatformWindowProc( HWND hWnd, UINT uMsg, WPARAM wParam, LPAR
|
|||||||
*/
|
*/
|
||||||
return 0;
|
return 0;
|
||||||
|
|
||||||
case WM_CANCELMODE:
|
|
||||||
/*
|
|
||||||
* The window manager sends this message when it detects a change
|
|
||||||
* that requires that an application cancel any modal state it has
|
|
||||||
* entered. If we've called SetCapture in the mouse button handler,
|
|
||||||
* call ReleaseCapture.
|
|
||||||
*/
|
|
||||||
if (setCaptureActive)
|
|
||||||
ReleaseCapture();
|
|
||||||
break;
|
|
||||||
|
|
||||||
case WM_MOUSEMOVE:
|
case WM_MOUSEMOVE:
|
||||||
{
|
{
|
||||||
#if defined(_WIN32_WCE)
|
#if defined(_WIN32_WCE)
|
||||||
|
Reference in New Issue
Block a user