Microsoft KB Archive/86464

{|
 * width="100%"|

INFO: New Win 3.1 API Functions Not Wrapped by MFC

 * }

Q86464

-

The information in this article applies to:


 * The Microsoft Foundation Classes (MFC), included with:
 * Microsoft C/C++ for MS-DOS, version 7.0
 * Microsoft Visual C++, versions 1.0, 1.5

-

SUMMARY
The following table shows the Microsoft Windows version 3.1 API functions that are not wrapped by the Microsoft Foundation Classes (MFC) and the reasons that they are not wrapped:

Windows 3.1 API                Reason Not Wrapped ---                --

_hread                         Not handle-based _hwrite                        Not handle-based CallNextHookEx                 Not handle-based CloseDriver                    Not graphical CopyCursor                     Infrequently used CopyIcon                       Infrequently used CreateScalableFontResource     Not handle-based DefDriverProc                  Did not wrap installable drivers EnableCommNotification         Did not wrap comms EnumFontFamilies               Infrequently used GetAspectRatioFilterEx         Added for future Win32 compatibility* GetBitmapDimensionEx           Added for future Win32 compatibility* GetBrushOrgEx                  Added for future Win32 compatibility* GetClipCursor                  Infrequently used GetCurrentPositionEx           Added for future Win32 compatibility* GetCursor                      Infrequently used GetDriverInfo                  Did not wrap installable drivers GetDriverModuleHandle          Did not wrap installable drivers GetFreeSystemResources         Not handle-based GetNextDriver                  Did not wrap installable drivers GetRasterizerCaps              Not handle based GetTextExtentEx                Added for future Win32 compatibility* GetTextExtentPoint             Added for future Win32 compatibility* GetViewportOrgEx               Added for future Win32 compatibility* GetWindowExtEx                 Added for future Win32 compatibility* GetWindowOrgEx                 Added for future Win32 compatibility* IsBadCodePtr                   Not handle-based IsBadHugeReadPtr               Not handle-based IsBadHugeWritePtr              Not handle-based IsBadReadPtr                   Not handle-based IsBadWritePtr                  Not handle-based IsDBCSLeadByte                 Not handle-based IsMenu                         Infrequently used IsTask                         Infrequently used LogError                       Not handle-based LogParamError                  Not handle-based lstrcpyn                       Not handle-based MoveToEx                       Added for future Win32 compatibility* OffsetViewportOrgEx            Added for future Win32 compatibility* OffsetWindowOrgEx              Added for future Win32 compatibility* OpenDriver                     Did not wrap installable drivers ResetDC                        Not defined in WINDOWS.H ScaleViewportOrgEx              Added for future Win32 compatibility* ScaleWindowExtEx               Added for future Win32 compatibility* SendDriverMessage              Did not wrap installable drivers SetBitmapDimensionEx           Added for future Win32 compatibility* SetViewportExtEx               Added for future Win32 compatibility* SetWindowExtEx                 Added for future Win32 compatibility* SetWindowOrgEx                 Added for future Win32 compatibility* SetWindowsHookEx               Infrequently used UnhookWindowsHookEx            Infrequently used

and the Win32 API, so there was no need to introduce into MFC these additional functions (usually ending in &quot;Ex&quot;) to account for those differences. Additional query words:
 * MFC will hide the differences in parameters accepted by the Win API

Keywords : kb16bitonly kbnokeyword kbMFC kbVC

Issue type :

Technology : kbAudDeveloper kbMFC