--- mstools/mfc/readme.txt 2018/08/09 18:21:00 1.1 +++ mstools/mfc/readme.txt 2018/08/09 18:22:19 1.1.1.2 @@ -6,7 +6,7 @@ *** for Microsoft Windows (R) NT (tm) *** *********************************************************************** - BETA RELEASE 1 + BETA OCTOBER 1992 This is the Beta Release of the Microsoft (R) Foundation Classes for Microsoft Windows NT. ENJOY! Release notes can be found at @@ -85,8 +85,8 @@ Support for Windows 3.1 features The Microsoft Foundation classes provide support for the enhancements provided in Windows version 3.1. The following features are described in technical notes in the - \NT\MSTOOLS\MFC\DOC directory and demonstrated in sample programs in - \NT\MSTOOLS\MFC\SAMPLES. These API functions are documented only in + \MSTOOLS\MFC\DOC directory and demonstrated in sample programs in + \MSTOOLS\MFC\SAMPLES. These API functions are documented only in the Help system. The following list describes the enhancements that can be used to develop applications for both Windows 3.0 and Windows 3.1. @@ -226,37 +226,30 @@ Windows NT Release Notes: unchanged from the 16 bit release. This release of MFC can be used interchangeably with the Microsoft C/C++ 7.0 release. + SAMPLES ARE NT VERSION BY DEFAULT: The makefiles for the sample + applications have been changed to build the NT VERSION BY DEFAULT. + If you wish to build a Windows version using these sources, you must + define WIN16MFC=1 when building. + -- In order to build the MFC sample applications you should have your environment set as follows: - set NTMFC=1 - set LIB=c:\mstools\lib (note this is not a ';' list) - set INCLUDE=c:\mstools\mfc\include;c:\mstools\h + set LIB=c:\mstools\lib;c:\mstools\mfc\lib + set INCLUDE=c:\mstools\h;c:\mstools\mfc\include These may also be set on the NMAKE command lines if you wish. If your installation is on another drive or in another directory, then you - should change c:\nt\mstools accordingly. - - NOTE: THE INCLUDE PATH ESTABLISHED BY THE NT SDK SETUP PROGRAM WILL - NOT WORK FOR MFC COMPILES. BEFORE COMPILING MFC CODE YOU MUST CHANGE - THE INCLUDE PATH AS DESCRIBED ABOVE. - --- The MFC\INCLUDE directory for this release contains copies of the - Windows NT header files. The copies have several modifications made - in order to make them more consistent with C++ and the Windows 3.1 - header files. This is only for this beta release and these changes - will be folded into the header files in MSTOOLS\H for the next release. - You must use these in order to successfully build the MFC library or - any MFC sample applications. + should change c:\mstools accordingly. -- Your PATH must include the Windows SDK Tools and Microsoft C/C++. --- Online documentation is available via QuickHelp (QH.EXE). The .HLP +-- Online documentation is available via WinHelp (MFC10WH.HLP) and is + installed by the SDK setup in MSTOOLS\BIN. + + Online documentation is also available via QuickHelp (QH.EXE). The .HLP files are located on the CD-ROM in MSTOOLS\HELP\QH. You must copy the help files and the QuickHelp application (QH.EXE) from the CD-ROM to your target hard disk yourself -- the NT SDK setup program will not install Quickhelp documentation. - Windows WinHelp files for MFC are not currently available. - -- This beta release of MFC does not include DLL support. -- Do not use the /Zp switch for MFC applications. If you do some system @@ -266,33 +259,19 @@ Windows NT Release Notes: from a .LIB. The MFC sample applications will emit this warning which can be ignored. +-- Owner draw menu items do not work correctly; OnMeasureItem is not + called. This will be fixed. + -- You may experience problems printing with the sample applications that print. --- The CHART sample application currently has several low level compiler - warnings that can be ignored. These will be addressed. - -- The MULTIPAD sample application currently has an inconsistency with the way it maintains the file MRU menu items. This will be fixed. -- The retail version of the MULTIPAD sample may fault on exit. This will be fixed in a future release. --- The "self-draw" control functionality for custom menu items (demonstated - in the CTRLTEST sample application) currently behaves inconsistently. - This will be fixed. - -- The MINSVRMI sample application may fault. This will be fixed. -- CListBox::FindStringExact and CComboBox::FindStringExact do not work correctly. This will be fixed. - --- Debugging C++ applications is quite "challenging" with this release. We - recommend the liberal use of trace statements and { _asm int 3 } lines - in your code. The NTSD debugger does not currently permit the setting - of breakpoints on C++ member functions. If you have global functions - that are not overloaded, then using the extern "C" construct will prevent - name decoration and permit the setting of breakpoints. If all else fails, - you can always debug your MFC application using C/C++ 7.0 - on a machine running CodeView 4.0 and Windows 3.1. The C++ expression - evaluator for WinDebug will be made available as soon as practical.