Re: [GD-Windows] WM_SYSCOMMAND documentation question

[Rich <leg...@xm...>]

In article <JDE...@ep...>,
    "Daniel Vogel" <vo...@ep...>  writes:

> The D3D sample applications return 1 in response to WM_SYSCOMMAND to prevent
> certain events from interfering with the app being fullscreen though I can't
> find any documention why 1 is returned. The MSDN docs state that 0 should be
> returned if the application handles WM_SYSCOMMAND so I'm wondering where the
> return value of 1 is documented.

I think Brian's analysis is correct.  From "Win32 Programming" by
Rector & Newcomer, pg. 904:

    "If you add your own menu items to the systme menu and, therefore,
    intercept the WM_SYSCOMMAND message, you must make sure you pass
    all unprocessed messages to the DefWindowProc function.  If you
    don't, the standard menu commands will be effectively disabled.
    They will look active to the user, but selecting them will have no
    effect."
-- 
"The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ:
          <http://www.xmission.com/~legalize/book/>
        izfree: Open source tools for Windows Installer
                <http://izfree.sourceforge.net>