{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "INSTALL EXE", "size": 6800, "date": "1991-11-11", "time": "3:00" }, { "name": "UNPAK EXE", "size": 25714, "date": "1991-11-11", "time": "3:00" }, { "name": "README COM", "size": 4217, "date": "1991-11-11", "time": "3:00" }, { "name": "BIN CA4", "size": 361472, "date": "1991-11-11", "time": "3:00" }, { "name": "BIN CA5", "size": 79103, "date": "1991-11-11", "time": "3:00" }, { "name": "BONK PAK", "size": 26119, "date": "1991-11-11", "time": "3:00" }, { "name": "CALC PAK", "size": 5984, "date": "1991-11-11", "time": "3:00" }, { "name": "CHECKERS PAK", "size": 24873, "date": "1991-11-11", "time": "3:00" }, { "name": "CURSOR PAK", "size": 4758, "date": "1991-11-11", "time": "3:00" }, { "name": "DISK1 DSK", "size": 5, "date": "1991-11-11", "time": "3:00" }, { "name": "DOC PAK", "size": 86706, "date": "1991-11-11", "time": "3:00" }, { "name": "EXAMPLE PAK", "size": 130834, "date": "1991-11-11", "time": "3:00" }, { "name": "FILEINFO INI", "size": 2373, "date": "1991-11-11", "time": "3:00" }, { "name": "FILELIST DOC", "size": 39153, "date": "1991-11-11", "time": "3:00" }, { "name": "GDIDEMO PAK", "size": 16830, "date": "1991-11-11", "time": "3:00" }, { "name": "INCLUDE PAK", "size": 101284, "date": "1991-11-11", "time": "3:00" }, { "name": "OWLDOC PAK", "size": 21923, "date": "1991-11-11", "time": "3:00" }, { "name": "OWLINC PAK", "size": 35621, "date": "1991-11-11", "time": "3:00" }, { "name": "RWCDEMO PAK", "size": 48720, "date": "1991-11-11", "time": "3:00" }, { "name": "TCINSTAL LZ", "size": 160845, "date": "1991-11-11", "time": "3:00" }, { "name": "README", "size": 20566, "date": "1991-11-11", "time": "3:00" } ] } ], "volume": "DISK 1" }, "2": { "dirs": [ { "path": "/", "files": [ { "name": "BIN CA2", "size": 361472, "date": "1991-11-11", "time": "3:00" }, { "name": "BIN CA3", "size": 361472, "date": "1991-11-11", "time": "3:00" }, { "name": "DISK2 DSK", "size": 5, "date": "1991-11-11", "time": "3:00" }, { "name": "FILEAPP PAK", "size": 2634, "date": "1991-11-11", "time": "3:00" }, { "name": "MFILEAPP PAK", "size": 3974, "date": "1991-11-11", "time": "3:00" }, { "name": "OWLDEMOS PAK", "size": 79615, "date": "1991-11-11", "time": "3:00" }, { "name": "PAINT PAK", "size": 8620, "date": "1991-11-11", "time": "3:00" }, { "name": "PROGTALK PAK", "size": 6092, "date": "1991-11-11", "time": "3:00" }, { "name": "RW CA2", "size": 361472, "date": "1991-11-11", "time": "3:00" }, { "name": "RWDOC PAK", "size": 24219, "date": "1991-11-11", "time": "3:00" } ] } ], "volume": "DISK 2" }, "3": { "dirs": [ { "path": "/", "files": [ { "name": "BWCC PAK", "size": 41546, "date": "1991-11-11", "time": "3:00" }, { "name": "CLASSEXM PAK", "size": 11410, "date": "1991-11-11", "time": "3:00" }, { "name": "CLIB PAK", "size": 116678, "date": "1991-11-11", "time": "3:00" }, { "name": "DISK3 DSK", "size": 5, "date": "1991-11-11", "time": "3:00" }, { "name": "MLIB PAK", "size": 114265, "date": "1991-11-11", "time": "3:00" }, { "name": "OWLLIB CA1", "size": 361472, "date": "1991-11-11", "time": "3:00" }, { "name": "RW CA3", "size": 60941, "date": "1991-11-11", "time": "3:00" }, { "name": "SYSINFO PAK", "size": 3551, "date": "1991-11-11", "time": "3:00" }, { "name": "TCW CA1", "size": 361472, "date": "1991-11-11", "time": "3:00" }, { "name": "TDWEXMPL PAK", "size": 139494, "date": "1991-11-11", "time": "3:00" } ] } ], "volume": "DISK 3" }, "4": { "dirs": [ { "path": "/", "files": [ { "name": "BIN CA1", "size": 361472, "date": "1991-11-11", "time": "3:00" }, { "name": "CLASSDBL PAK", "size": 6191, "date": "1991-11-11", "time": "3:00" }, { "name": "CLASSDLL PAK", "size": 6370, "date": "1991-11-11", "time": "3:00" }, { "name": "CLASSINC PAK", "size": 47904, "date": "1991-11-11", "time": "3:00" }, { "name": "DEBUG CA1", "size": 361472, "date": "1991-11-11", "time": "3:00" }, { "name": "DISK4 DSK", "size": 5, "date": "1991-11-11", "time": "3:00" }, { "name": "RW CA1", "size": 361472, "date": "1991-11-11", "time": "3:00" }, { "name": "STEPS PAK", "size": 27587, "date": "1991-11-11", "time": "3:00" }, { "name": "UTILS PAK", "size": 36078, "date": "1991-11-11", "time": "3:00" } ] } ], "volume": "DISK 4" }, "5": { "dirs": [ { "path": "/", "files": [ { "name": "CLASSDBS PAK", "size": 6173, "date": "1991-11-11", "time": "3:00" }, { "name": "CLASSL PAK", "size": 6166, "date": "1991-11-11", "time": "3:00" }, { "name": "CLASSLIB PAK", "size": 127608, "date": "1991-11-11", "time": "3:00" }, { "name": "CLASSS PAK", "size": 6155, "date": "1991-11-11", "time": "3:00" }, { "name": "CLASSSRC PAK", "size": 29647, "date": "1991-11-11", "time": "3:00" }, { "name": "DEBUG CA2", "size": 79803, "date": "1991-11-11", "time": "3:00" }, { "name": "DISK5 DSK", "size": 5, "date": "1991-11-11", "time": "3:00" }, { "name": "LLIB PAK", "size": 118034, "date": "1991-11-11", "time": "3:00" }, { "name": "OWLLIB CA2", "size": 99070, "date": "1991-11-11", "time": "3:00" }, { "name": "SLIB PAK", "size": 112750, "date": "1991-11-11", "time": "3:00" }, { "name": "TCREM EXE", "size": 3072, "date": "1991-11-11", "time": "3:00" }, { "name": "TCW CA2", "size": 113081, "date": "1991-11-11", "time": "3:00" }, { "name": "TTT PAK", "size": 5383, "date": "1991-11-11", "time": "3:00" }, { "name": "XLIB PAK", "size": 82418, "date": "1991-11-11", "time": "3:00" } ] } ], "volume": "DISK 5" } }, "desc_file": "README", "desc_text": " Welcome to Turbo C++ for Windows\r\n --------------------------------\r\n\r\n This README file contains important information about Turbo C++\r\n for Windows. For the latest information about Turbo C++ for\r\n Windows and its accompanying programs and manuals, read this\r\n file in its entirety.\r\n\r\nTABLE OF CONTENTS\r\n-----------------\r\n1. How to Get Help\r\n2. Installation\r\n3. Features\r\n4. Important Information\r\n5. Testing Your Expanded Memory\r\n6. Corrections to the Documents\r\n\r\n\r\n 1. HOW TO GET HELP\r\n-------------------\r\n If you have any problems, please read this file, the\r\n HELPME!.DOC and other files in your DOC subdirectory, and the\r\n Turbo C++ for Windows manuals first. If you still have a\r\n question and need assistance, help is available from the\r\n following sources:\r\n\r\n 1. Type GO BPROGB on the CompuServe bulletin board system for\r\n instant access to the Borland forums with their libraries of\r\n technical information and answers to common questions.\r\n\r\n If you are not a member of CompuServe, see the enclosed\r\n special offer, and write for full details on how to receive\r\n a free IntroPak containing a $15 credit toward your first\r\n month's on-line charges.\r\n\r\n 2. Check with your local software dealer or users' group.\r\n\r\n 3. Borland's TECHFAX service. Call (800) 822-4269 for a FAX \r\n catalog of entries.\r\n\r\n 4. If you have an urgent problem that cannot wait and you have\r\n sent in the license agreement that came with the package,\r\n you may call the Borland Technical Support Department at\r\n (408) 438-5300. Please have the following information ready\r\n before calling:\r\n\r\n a. Product name and serial number on your original\r\n distribution disk. Please have your serial number ready\r\n or we will be unable to process your call.\r\n\r\n b. Product version number. The version number for Turbo\r\n C++ for Windows can be displayed by pressing Alt-H/A.\r\n\r\n c. Computer brand, model, and the brands and model numbers of\r\n any additional hardware.\r\n\r\n d. Operating system and version number. (The version number\r\n can be determined by typing VER at the MSDOS prompt, or\r\n use the Windows utility WINVER for the Windows version.)\r\n\r\n e. Contents of your AUTOEXEC.BAT file.\r\n\r\n f. Contents of your CONFIG.SYS file.\r\n\r\n\r\n 2. INSTALLATION\r\n----------------\r\n\r\n You MUST use the INSTALL program to install Turbo C++ for\r\n Windows. The files on the distribution disks are all archived\r\n and have to be properly assembled. You cannot do this by hand!\r\n\r\n Turbo C++ for Windows includes a Windows installation program\r\n that will create the appropriate subdirectories and copy the\r\n software on to your hard disk. To run the installation program\r\n from Drive A type\r\n\r\n WIN A:INSTALL\r\n\r\n or, if Windows is active, select the program manager's File|Run\r\n command and type\r\n\r\n A:INSTALL\r\n\r\n Note that this version of the installation program runs under\r\n Windows standard or 386 Enhanced modes only. After\r\n installation, make sure you insert \\TCWIN\\BIN - or whatever you\r\n selected as your BIN directory - into your DOS path\r\n so the DLL and executable files can be found.\r\n\r\n If you use a screen saver such as After Dark or Borland's Screenery,\r\n you should disable it before running the INSTALL program.\r\n\r\n - Note: The list of files is contained in a separate file\r\n called FILELIST.DOC, which will appear in the target\r\n directory you specify during installation.\r\n\r\n - Make sure you select the \"LAN Windows configuration\" option\r\n if Windows is executed from your network.\r\n\r\n - If you have previously installed Resource Workshop, make sure\r\n that you remove the directory of that version from your path. The\r\n version included on these disks supercedes previous versions.\r\n\r\n - If you use a Windows command shell other than Program Manager,\r\n you may not get a Turbo C++ group installed for Windows. If\r\n you don't, use File|New in Program Manager (or the equivalent\r\n command in your shell) to add items for the following files:\r\n\r\n Description EXE file Default path\r\n ----------- -------- ------------\r\n TURBO C++ TCW.EXE C:\\TCWIN\\BIN\r\n WORKSHOP WORKSHOP.EXE C:\\TCWIN\\BIN\r\n IMPORT LIB IMPLIBW.EXE C:\\TCWIN\\BIN\r\n DEBUG TDW.EXE C:\\TCWIN\\BIN\r\n FCONVERT FCONVERT.EXE C:\\TCWIN\\BIN\r\n\r\n\r\n You should read the rest of this README file to get further\r\n information about this release before you do the installation.\r\n\r\n\r\n 3. FEATURES\r\n------------\r\n\r\n Turbo C++ for Windows 3.0 includes complete support for Windows\r\n programming, as well as big speed and capacity gains. Here are\r\n some important features:\r\n\r\n - A Windows hosted IDE (TCW.EXE), including a class hierarchy \r\n browser.\r\n\r\n - Turbo Debugger support for breakpoints with multiple conditions\r\n and for viewing selectors.\r\n\r\n - C++ 2.1 support, including the new nested class specifications,\r\n and support of C++ 3.0 templates.\r\n\r\n - Added library functions for compatibility with other runtime \r\n libraries, and addition of support for long double parameters\r\n in math functions. (Please see the Library Reference for details.)\r\n\r\n - EasyWin, which includes library support for stdio.h and\r\n conio.h functions under Windows. (Please see the Turbo C++\r\n for Windows User's Guide for details.)\r\n\r\n - FCONVERT.EXE - Converts OEM to ANSI Character Set\r\n\r\n DOS text files use the OEM character set; Windows text\r\n files generally use the ANSI character set. The demo\r\n program, FCONVERT.EXE converts data back and forth between\r\n these formats. The only text files that will be affected\r\n are those containing international characters (ASCII values\r\n above 128) like the umlaut, etc. Not all OEM characters are\r\n present in the ANSI character set, and vice versa. \r\n Therefore, converting between these character sets may\r\n produce a mapping that is not reversible. Refer to your\r\n Windows documentation for further information about ANSI\r\n vs. OEM character sets.\r\n\r\n - IMPLIBW.EXE, a Windows-hosted import librarian.\r\n\r\n - ObjectWindows Library, an application framework that will ease\r\n the development of applications for Windows.\r\n\r\n 4. IMPORTANT INFORMATION\r\n-------------------------\r\n\r\n - Turbo C++ for Windows only supports Protected Mode Windows target\r\n files.\r\n\r\n - If you get a \"floating point formats not linked\" message at\r\n runtime, put the following somewhere in your source files:\r\n\r\n extern void _floatconvert();\r\n #pragma extref _floatconvert\r\n\r\n This will force inclusion of floating point formats, which\r\n may not be linked to reduce executable size.\r\n\r\n - Make sure that you use the Options|Compiler|Entry|\r\n Windows explicit functions exported when using the\r\n fastcall modifier. The same applies when using the fastcall\r\n compilation option (Options|Compiler|Entry|Register.)\r\n\r\n\r\n COMPILER\r\n\r\n - Note that the Generate COMDEFs choice under\r\n Options|Compiler|Code Generation is only supported in the C\r\n language. Linker errors will result if you attempt to use a\r\n communal variable in C++.\r\n\r\n - The macros min() and max() are not defined when stdlib.h is\r\n compiled as C++ (to allow their use in 3rd party libraries,\r\n etc.).\r\n\r\n - Note that SYMDEB creates .SYM files for use in debugging;\r\n Turbo C++ for Windows creates .SYM files for pre-compiled\r\n headers. They are not compatible and collisions should be\r\n avoided by setting the name of the pre-compiled header file\r\n (using -H=filename).\r\n\r\n - There is now full support of distance modifiers (near and\r\n far) used for class member pointers. Here are two sample\r\n declarations and their meanings:\r\n\r\n void (A::* far var) ();\r\n\r\n this is a far variable 'var' of type 'void (A::*)()';\r\n\r\n void (far A::* var) ();\r\n\r\n this is a 'default distance' variable 'var' of type\r\n\t'void (far A::*)()'\r\n\r\n - You must use \"smart callbacks\" - Options|Compiler|Entry/Exit\r\n Code|Windows smart callbacks - if your application uses\r\n classes whose code is in a DLL. This applies especially in\r\n the case of a class implemented in an EXE which is derived\r\n from another implemented in a DLL, which normally applies for\r\n users of OWL and other object-oriented class libraries.\r\n\r\n IDE\r\n\r\n - If you run File|Printer setup from the IDE (or another Windows\r\n application which has printer setup support) under the Windows\r\n 3.0 debugging kernel, you will get a System Error from Windows.\r\n You must switch to the NODEBUG version to run this option.\r\n\r\n EXAMPLE PROGRAMS\r\n\r\n - When you are running any example programs that come with .PRJ\r\n files, if you didn't use the standard directories when you\r\n installed Turbo C++ for Windows you will have to change the\r\n .PRJ file to reflect your actual directory setup. Do this\r\n from inside Turbo C++ for Windows with Alt-O/D.\r\n\r\n\r\n LINKING C++ WITH C\r\n\r\n - Linking C++ modules with C modules requires the use of a\r\n linkage specification. Prototypes for C functions within C++\r\n modules must be in one of the following forms:\r\n\r\n extern \"C\" declaration\r\n extern \"C\" { declarations }\r\n\r\n For example, if a C module contains these functions:\r\n\r\n char *SCopy(char*, char*);\r\n void ClearScreen(void)\r\n\r\n they must be declared in a C++ module in one of the\r\n following ways:\r\n\r\n extern \"C\" char *SCopy(char*, char*);\r\n extern \"C\" void ClearScreen(void);\r\n\r\n or\r\n\r\n extern \"C\" {\r\n char *SCopy(char*, char*);\r\n void ClearScreen(void);\r\n }\r\n\r\n Failure to do so will result in \"Undefined symbol\" errors\r\n during link. For further examples, see the standard header\r\n files.\r\n\r\n\r\n TURBO DEBUGGER\r\n\r\n - You cannot set a window message breakpoint by using a window\r\n handle in an ObjectWindows application. You can, however, set\r\n window message breakpoints with ObjectWindows applications:\r\n enable ObjectWindows support (use TDWINST and choose\r\n Options|Source Debugging|OWL Window Messages), then use\r\n window object names to set message breakpoints.\r\n\r\n - The first time a program is run under TDW, mouse messages are\r\n processed normally. However, on every subsequent execution of\r\n that program, you must press a key on the keyboard before\r\n mouse messages can be processed.\r\n\r\n\r\n Super VGA support\r\n =================\r\n\r\n TDW handles most of the popular 2, 4, and 16-color high-\r\n resolution Super VGA modes. If your card isn't supported\r\n correctly, or if you want to debug in a 256-color mode, you'll\r\n need to use a special Super VGA DLL.\r\n\r\n Currently, the following DLLs are supplied with your language\r\n compiler to support these SVGA cards and modes:\r\n\r\n TSENG.DLL (TSENG ET-3000 /ET-4000 based cards)\r\n 640x480x256\r\n 800x600x256\r\n 1024x768x256\r\n\r\n\r\n ATI.DLL (ATI VGA Wonder card)\r\n 640x480x256 (See the NOTE below)\r\n 800x600x256\r\n\r\n To use a Super VGA DLL, copy the appropriate DLL file into the\r\n directory that contains the TDW executable (usually the BIN\r\n subdirectory of your language compiler directory) and rename it\r\n to TDVIDEO.DLL.\r\n\r\n TDW, upon loading, looks for TDVIDEO.DLL in the same directory\r\n that harbors TDW.EXE. If it finds the file, TDW accesses the\r\n DLL as it's needed. TDW makes calls to the DLL to handle the\r\n entire video screen switching context. The DLL accomplishes the\r\n screen switching by allocating a buffer as it gets loaded.\r\n Graphic screen contents are then saved to this buffer as TDW\r\n enters text mode. The DLL restores the graphics screen from\r\n this buffer as TDW exits text mode. Memory allocated for the\r\n buffer is freed when the DLL is unloaded.\r\n\r\n If there is an error loading TDVIDEO.DLL, or if the DLL doesn't\r\n support the selected card or mode, TDW will report the error in\r\n a Windows dialog box. When this happens, TDW will unload\r\n TDVIDEO and exit. If this situation occurs, delete TDVIDEO.DLL,\r\n or select a mode that is supported by the DLL.\r\n\r\n If you're debugging an application that's been built with\r\n EasyWin, you may see incorrect screen painting as you step over\r\n lines of code that make calls to STDIO functions. In this case,\r\n edit the TDVIDEO.INI file and set the Int2FAssist option to\r\n \"yes\" (see the NOTE below).\r\n\r\n NOTE: The ATI mode 640x480x256 and EasyWin applications may\r\n require some special handling. An option called Int2FAssist\r\n in the TDVIDEO.INI file allows this mode to work correctly on\r\n most systems. The behaviour is as follows: When you set\r\n \"Int2FAssist=yes\", TDVIDEO makes Windows tell all sub-windows\r\n on the screen to re-paint themselves as the DLL is loaded.\r\n This allows the user screen to be viewed when Stepping,\r\n Tracing, or Running your application. It will not, however,\r\n switch to the user screen when you press since TDW\r\n is still in control (it doesn't allow Windows to process any\r\n messages). If you also set \"SaveWholeScreen=yes\", then will show the user screen (TDVIDEO will now copy the\r\n screen for you). The drawback to enabling SaveWholeScreen is\r\n that it will take longer to Step or Trace if TDW needs to\r\n switch back to the user screen for that particular\r\n instruction. Also, extra messages are getting passed to your\r\n application that normally would not be passed. This may\r\n effect the debugging of certain pieces of code (like finding\r\n a bug in an owner-draw procedure). In these cases, you will\r\n not want to use this video mode.\r\n\r\n\r\n TDVIDEO.INI\r\n -----------\r\n\r\n You can create the file TDVIDEO.INI with any ASCII text editor.\r\n This file is used to control how TDVIDEO.DLL functions.\r\n TDVIDEO.INI must be located in WINDOW's main directory (usually\r\n C:\\WINDOWS). The options in TDVIDEO.INI are handled by the DLL\r\n itself and are therefore subject to change with newer versions\r\n of the DLLs. The DLLs use the following options, written in any\r\n order, under the heading [VideoOptions]:\r\n\r\n SaveWholeScreen -- default = 'no'\r\n Int2FAssist -- default = 'no'\r\n DebugFile -- default = '' (no logging will occur)\r\n\r\n The SaveWholeScreen and Int2FAssist can be set to either 'yes'\r\n or 'no'. DebugFile can be either blank, or it can be set to a\r\n specific filename.\r\n\r\n *** SaveWholeScreen ***\r\n\r\n This option, normally set to 'no', determines whether the\r\n entire screen (512k - 64k from 8 planes) will be saved (the\r\n entire graphics screen is cleared when switching to it) or if\r\n only the top 32K of planes 0 through 3 will be saved (the\r\n entire screen is NOT cleared when switching modes.)\r\n\r\n Saving the whole screen is rarely needed, but is provided in\r\n case you're using a nonstandard card that needs the whole\r\n screen to be saved.\r\n\r\n *** Int2FAssist ***\r\n\r\n This option, normally set to 'no', tells TDVIDEO, to make a\r\n special Int 2F call before switching video modes. This call\r\n tells the current Windows screen driver (VGA.DRV for standard\r\n VGA mode) what's happening. The desired side-effect of this\r\n call is to make Windows tell all of its child windows to re-\r\n paint themselves. This option is provided only for support on\r\n an ATI Super VGA video mode and for applications built using\r\n EasyWin (see NOTE above). However, be aware, that this option\r\n can affect the other supported modes if it's enabled (use\r\n this option only if absolutly necessary).\r\n\r\n *** DebugFile ***\r\n\r\n TDVIDEO.DLL normally doesn't save any debugging information.\r\n If you're having problems using a special DLL, the DebugFile\r\n option can be used to specify the path and filename of a log\r\n file. Information logged to this file can be used if you need\r\n to contact Borland's Technical Support. Information logged\r\n consists of the Date/Time, the version of the DLL, the name\r\n of the Windows screen driver that is currently in use, the\r\n state of all .INI options, and a listing of all the calls to\r\n the DLL's functions.\r\n\r\n For example, if you want your DLL to save the entire screen\r\n and log information to a file named C:\\WINDOWS\\TDVIDEO.LOG,\r\n create a file called TDVIDEO.INI in the WINDOWS directory\r\n that contains the following commands:\r\n\r\n [VideoOptions]\r\n SaveWholeScreen=yes\r\n DebugFile=c:\\windows\\tdvideo.log\r\n\r\n\r\n CLASS LIBRARY\r\n\r\n - If you used the add(), addAt(), or getItemsInContainer()\r\n member functions of the Array class in Turbo C++ for Windows\r\n 2.0 applications, note that their behavior has changed\r\n slightly. The following rules apply to these and related\r\n functions:\r\n\r\n 1. add() will insert its argument at the lowest available\r\n location in the Array. This location is known as the\r\n \"insertion point\".\r\n\r\n 2. detach() will remove its argument from the Array, and if\r\n that Object is located below the insertion point, it\r\n will move the elements above the Object being removed\r\n and below the insertion point down one position, so that\r\n the elements below the insertion point remain\r\n contiguous. The insertion point, of course, moves down\r\n one.\r\n\r\n 3. if the location specified in a call to addAt() is below\r\n or at the insertion point, the elements above the\r\n specified location and below the insertion point are\r\n moved up one position, and the Object is inserted. The\r\n insertion point moves up one.\r\n\r\n 4. if the location specified in a call to addAt() is above\r\n the insertion point, the Object is inserted at that\r\n location, replacing any Object that may have been placed\r\n there previously.\r\n\r\n 5. getItemsInContainer() returns the number of elements\r\n below the current insertion point. If you use addAt()\r\n to add elements above the insertion point, they will not\r\n affect the value returned by getItemsInContainer(). \r\n This is a change from the behavior in the previous\r\n version of the class library.\r\n\r\n - Only the small and dynamic link class libraries are supplied\r\n in this release. If you need other models, use the project\r\n files supplied under the CLASSLIB\\OBJS subdirectories to\r\n build them. For instance, to build a medium model library\r\n without templates, create a directory called M under\r\n \\CLASSLIB\\OBJS, and copy the TCLASSL.PRJ file from the L\r\n directory to a file called TCLASSM.PRJ in your new M\r\n directory. Then load TCW.EXE, used Project|Open to open\r\n TCLASSM.PRJ, and change Options|Compiler|Code generation|\r\n Model to Medium.\r\n\r\n OWL\r\n\r\n - You must rebuild the class libraries in the appropriate model\r\n for the intended OWL model if they don't already exist - see\r\n paragraph above.\r\n\r\n - Note that you must use the TWindow member function AssignMenu\r\n to assign a window's Attr.Menu member and to load a menu for\r\n that window.\r\n\r\n 6. CORRECTIONS TO THE DOCUMENTS\r\n---------------------------------\r\n\r\nObjectWindows User's Guide\r\n--------------------------\r\n Chapter 2, \"Stepping through Windows\"\r\n -------------------------------------\r\n Page 22\r\n -------\r\n The sentence that begins \"These libraries are located in the library \r\n directories listed in the following table...\" should instead read\r\n \"Table 2.2 lists the file names of the static ObjectWindows library \r\n and static container class library for each supported memory model.\"\r\n\r\n Chapter 11, \"Dialog objects\"\r\n ----------------------------\r\n Page 151\r\n --------\r\n In the TSampleWindow::GetName fragment shown, a line is in error. \r\n The line that begins\r\n if ( ExecDialog(new TInputDialog(this...\r\n should read\r\n if ( GetApplication()->ExecDialog(new TInputDialog(this...\r\n\r\n Chapter 12, \"Control objects\"\r\n ----------------------------\r\n Page 158+\r\n ---------\r\n Although it doesn't specifically state so, TListBox and its member\r\n functions can be used with both single- and multiple- selection\r\n list boxes." }