Contents of the FoxPro for Macintosh LCK Readme File

 Last reviewed: June 3, 1996
Article ID: Q113048
The information in this article applies to:
  • Microsoft FoxPro Library Construction Kit for Macintosh, version 2.5b

SUMMARY

Below is the complete FoxPro for Macintosh Library Construction Kit (LCK) "Readme" file located on the Disk 1 - Setup disk.

MORE INFORMATION

********************************************************** 

                    Release Notes for
Microsoft(R) FoxPro(R) for Apple(R) Macintosh(R) Library Construction Kit 

      (C)1993 Microsoft Corporation. All Rights Reserved.
This file provides information not contained in the Library Construction Kit documentation, and provides corrections to the documentation. **********************************************************

Contents

Part 1: Installing the Library Construction Kit Part 2: Additional Information Part 3: Changes to Documentation Since Printing

Part 1: Installing the Library Construction Kit To install the Library Construction Kit for Macintosh, follow these steps:

  1. Turn off any virus protection programs.
2. Insert the disk labeled "Disk 1 - Setup" in the disk drive. 3. Copy the FoxLCK and ASLM Development Tools folders to your hard 
   disk.
4. Copy the UserStartup-LCK file to your MPW folder.

Sample code is available in the FoxLCK:Source folder for you to use.

Part 2: Additional Information

For the most up-to-date information about Microsoft FoxPro for Macintosh and other Microsoft products, see the Microsoft Knowledge Base and the Microsoft Software Library.

The Microsoft Knowledge Base contains more than 40,000 detailed articles with technical information about Microsoft products, bug lists, fix lists, documentation errors, and answers to commonly asked technical questions-- all available through the Microsoft TechNet compact disc, the Microsoft Developer Network compact disc, and the Internet.

The Microsoft Software Library is an information resource that can be accessed through the same sources as the Microsoft Knowledge Base. This library contains sample programs, device drivers, patches, software updates, and programming aids. To help you quickly evaluate choices, a brief text description is displayed when you view each item. Additionally, many items have an associated Microsoft Knowledge Base article that more fully describes the information.

Contents

1. Customizing MPW 2. _Alloca() Caution 3. Including PRO_EXT.H 4. Installing .MLB Files 5. Errors While Using _Execute

1. Customizing MPW

Before you create shared libraries, customize MPW to work with your source files. You can use the provided example files to test your changes.

To customize the example files: 1. Open UserStartup-LCK and change any path references to match your 

   volume name.
   NOTE Volume names cannot contain spaces.
2. To enable these changes, exit MPW, then restart MPW. 3. Set your default directory to <your volume>:FoxLCK:Source: 4. In the Source folder, open Makefile. 5. Change the ROOTDIR setting to match your volume name.

Now, MPW is customized to produce a shared library. Verify this by building a sample library.

To create a sample shared library: 1. In the MPW Worksheet window, type MAKE and press Command+Return. 2. Highlight the output from MAKE and execute it by pressing Command+Return.

A file called TestLib.MLB will be created in your FoxLCK:Source folder.

To test the sample shared library: 1. Drag TestLib.MLB to your Systems:Extensions folder. 2. Run FoxPro. 3. In the Command Window, type SET LIBRARY TO TestLib.

Event messages from the library will appear in your main FoxPro window. To stop the output, use the command SET LIBRARY TO with no parameter.

2. _Alloca() Caution

The following caution is part of the description for _Alloca() in Chapter 10 of the documentation. Though the sample code in EXAMPLES.DBF has been modified to illustrate this, the caution still applies to any code you write.

CAUTION Some C compilers, such as MPW C, do not support memory allocation from the stack; calls to _Alloca() will have unpredictable results. Instead, use local variables, or calls to _AllocHand() and _FreeHand(), in your code to reserve memory.

3. Including PRO_EXT.H

Definitions in PRO_EXT.H might conflict with definitions in other include files you are using. For better results when you compile, put PRO_EXT.H last in your list of include files..

4. Installing .MLB Files

Built .MLB files must be placed in the EXTENSIONS folder.

IMPORTANT Do not build directly to the EXTENSIONS folder. Send output to a work directory, then move the file to the EXTENSIONS folder afterward.

5. Errors While Using _Execute

If an error occurs in the program passed to _Execute, the error displays as a normal program error, with Cancel, Suspend, and Ignore buttons. To prevent this display, make sure the program has its own error handler.

Part 2: Changes to Documentation Since Printing

Any changes to example code in the documentation should also be changed in the EXAMPLES.DBF file.

Page 69

In the example code for _ActivateIdle, change: 
    void FAR IdleHandler(WHandle wh, EventRec *ev)
to: 
    void FAR IdleHandler()
The two parameters are ignored on the Macintosh, and can cause problems on Windows.

Page 99

In the example code for _DeActivateIdle, change: 
    void FAR IdleHandler(WHandle wh, EventRec *ev)
to: 
    void FAR IdleHandler()

Page 321

Add a note to the end of the Description column for the rMouseDown event: 

   N/A for Macintosh.
Microsoft and FoxPro are registered trademarks of Microsoft Corporation.

Apple and Macintosh are registered trademarks of Apple Computer, Inc.

Additional reference words: FoxMac LCK 2.50b
KBCategory: kbreadme
KBSubcategory:

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 3, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.