C language function:DefFrameProc sample codes

Search sample code in the internet.It is the result.


TITLE : DefFrameProc function (Windows)
LRESULT WINAPI DefFrameProc(.......
http://msdn.microsoft.com/en-us/library/windows/desktop/ms644924(v=vs.85).aspx


TITLE : 【PB】PowerBuilder API Site
FUNCTION ulong DefFrameProc(ulong hwnd,ulong hWndMDIClient,ulong wMsg,ulong wParam,ulong lParam) LIBRARY "user32.dll" ALIAS FOR "DefFrameProcA".......
http://www.360doc.com/content/13/0216/20/11408198_266000549.shtml
TITLE : Win32 Multiple Document Interface Source
DefFrameProc(hWnd, hWndClient, Msg, wParam, lParam);.......
http://www.alsprogrammingresource.com/mdi.html
TITLE : Win32 Multiple Document Interface Source
return DefFrameProc(hWnd, hWndClient, Msg, wParam, lParam);.......
http://www.alsprogrammingresource.com/mdi.html
TITLE : Win32 Tutorial - Lesson 8: Management of a Window
You start an MDI like the types of applications we have created so far. One of the primary differences is that the window procedure must return the DefFrameProc() function. Its syntax is:.......
http://www.functionx.com/win32/Lesson08.htm
TITLE : Win32 Tutorial - Lesson 8: Management of a Window
LRESULT DefFrameProc(HWND hWnd,.......
http://www.functionx.com/win32/Lesson08.htm
TITLE : App Part 4: Multiple Document Interface
Before we create our MDI window we need to make a change to the default message processing that goes on in our Window Procedure... since we're creating a Frame window that will host an MDI Client, we need to change the DefWindowProc() call to DefFrameProc() which adds specialized message handling for Frame Windows,.......
http://www.winprog.org/tutorial/app_four.html
TITLE : App Part 4: Multiple Document Interface
return DefFrameProc(hwnd, g_hMDIClient, msg, wParam, lParam);.......
http://www.winprog.org/tutorial/app_four.html
TITLE : App Part 4: Multiple Document Interface
ccs.idFirstChild is a number to use as the first ID for the items the Client adds to the Window menu... you want this to be easily distinguishable from your own menu identifiers so you can handle your menu commands and pass the Window menu commands to DefFrameProc() for processing. In the example I specify an identifier defined as 50000, high enough that I know none of my menu command id's will be above it........
http://www.winprog.org/tutorial/app_four.html
TITLE : App Part 4: Multiple Document Interface
DefFrameProc(hwnd, g_hMDIClient, msg, wParam, lParam);.......
http://www.winprog.org/tutorial/app_four.html
TITLE : App Part 4: Multiple Document Interface
I've added a default: case which will catch all commands that I didn't process directly and do a check to see if the value is greater than or equal to ID_MDI_FIRSTCHILD. If it is, then the user has clicked on one of the Window menu items and we send the message on to DefFrameProc() for processing........
http://www.winprog.org/tutorial/app_four.html
search Google

https://www.google.com/#q=DefFrameProc