Contents of the Library Construction Kit README.TXT FileID: Q108822
WINDOWS | MS-DOS
kbreadme
The information in this article applies to:
SUMMARYBelow is the complete FoxPro Library Construction Kit (LCK) for Windows and MS-DOS README.TXT file. This file is found in the main Library Construction Kit directory (by default FOXLCK).
MORE INFORMATION
**********************************************************
**********************************************************
CONTENTSPart Description ---- ----------- 1 Additions to Documentation Since Printing 2 Corrections to Documentation Since Printing
Part 1: Additions to Documentation Since PrintingThe EXAMPLES directory contains a FoxPro database with all the example code that is used in the manual. Simply search for the function with example code you wish to copy and then extract the code from the memo field. You are free to use this code in your own applications.
The following function has been added: WHANDLE _WMainWindow( ) Description: _WMainWindow( ) returns the WHANDLE of the main FoxPro window in FoxPro for Windows or of the FoxPro desktop in FoxPro for MS-DOS. Example: The following example writes a message to the main FoxPro window in FoxPro for Windows or to the FoxPro desktop in FoxPro for MS-DOS. FoxPro Code:
C Code:
Part 2: Corrections to Documentation Since PrintingPage 2: In the Reverse.C example: The comment "/* Check to see if we can allocate the memory needed. */" is missing the end comment marker */. The three-line comment "Since this routine doesn't call any functions that cause memory reorganization . . . prior to de-referencing them (_HandToPtr)" is missing the single line comment marker // in the second and third lines. This statement:
should be:
Change the "<<" in the original example to "<".
Page 5: The Value Structure Fields table should include the General FoxPro data type. The applicable fields and their values are listed below: val.ev_type = 'G' val.ev_width = FCHAN val.ev_long = length of general field val.ev_real = offset of general field Page 6: The data type FPFI, a FAR pointer to a function returning Int, is mistakenly listed as "FPDI".
Page 7: In addition to the Point, Rect and EventRec data structures, PointP and RectP should be included. PointP and RectP are identical to Point and Rect except that Point and Rect coordinates are in rows and columns while PointP and RectP coordinates are in pixels. Page 12: The example
should be:
Use an expression ==, a closed parenthesis at the end of
the first line, and a semicolon at the end of the second
line.
Page 22: When compiling a .PLB library in Microsoft C7 or Visual C/C++, you need to use the following command line: CL /O /ALw /Zp /GW When linking a .PLB library in Microsoft C7 or C8, you need to use the /NOE and /NONULLS switches. Leaving out /NOE can cause redefinition errors. Leaving out /NONULLS will cause FoxPro not to recognize the .PLB as a valid library.
Page 25: The section heading for the makefile on this page is incorrect. It should say "Microsoft C/C++ Makefile for MS-DOS" instead of "WATCOM C Makefile for MS-DOS."
Page 26: The makefile on this page should have the following section heading: "WATCOM C Makefile for MS-DOS."
Page 39: The example doesn't work as intended in all cases. To have it work, you need to change the following line:
to:
Page 85: The following information applies to the _DBSeek( ) function: The struct Value passed to _DBSeek( ) (via a pointer) must be of ev_type == 'N' when seeking a numeric field even if that field has 0 decimal digits. If the struct Value has an ev_type of 'I', _DBSeek( )will return the internal error number -302, "Data type mismatch."
Page 109: The struct EDENV documented with _EdGetEnv( ) isn't correct. The actual structure from PRO_EXT.H appears as follows: NOTE: (R) indicates that this member is read-only and typedef struct
{
} EDENV;
Page 122: The syntax for _EdOpenFile() is missing the "mode" argument. It should read:
The following Mode options are available:
FO_READONLY, FO_WRITEONLY, FO_READWRITE.
Page 315: zoomEvent is a FoxPro for MS-DOS event. You can't trap for this event in FoxPro for Windows.
In an EventHandler in the FoxPro for Windows Library Construction Kit, if you make a call to FoxPro which generates another event, the original event record may be changed. This won't happen in the FoxPro for MS-DOS Library Construction Kit. The following example illustrates this:
FAR EventHandler(WHandle theWindow, EventRec FAR *ev)
{
FAR EventExit()
{
FAR Quotes(ParamBlk FAR *parm)
{
}
FoxInfo myFoxInfo[] = { };
FoxTable _FoxTable = { };
Additional reference words: FoxDos FoxWin 2.50 2.50a 2.50b lck
KBCategory: kbreadme
KBSubcategory: FxotherReadme
|
|
Last Reviewed: May 1, 1996 © 1999 Microsoft Corporation. All rights reserved. Terms of Use. |