
ReadMe.txt - ADS MFC Application

Author: Dave Geary (CIS: 100012,2000) - June 1996

Description
   The files provided form the base of a ADS application based on
   Microsoft's MFC library for Windows.  The resulting project is
   intended to provide a framework within which developers can
   define their own ADS command functions, using both MFC and
   Windows API functions, in addition to the standard ADS library
   functions.

Requirements
   The project files were created and tested with MS Visual C++ 2.2
   and AutoCAD R13 (c4) under Windows NT.  However, they should also
   be compatible with MSVC 4.0/4.1 and Win 3.11/Win95.

Getting Started
   If you haven't already done so, extract the files by running the
   zipped executable with the -d option to retain the directory
   structure.  If you have already extracted the files into a single
   directory, create two subdirectories - 'hlp' and 'res' - and move
   the files listed into them:
      hlp - afxdlg.rtf
      res - AdsApp.ico/AdsApp.rc2
   Open the .MAK file within Visual C++.  It is recommended that
   the project is compiled immediately to ensure that it is okay
   and your system is set up correctly, before making *any* changes
   that might affect the build.

   Even with compiler warnings set to level 4, the project should
   compile with *no* warnings.  If there are any, check your VC++
   settings first before making any changes to the project/code.
   After compiling, test it in AutoCAD.  The project defines a
   single test command, APPABOUT, that displays a simple MFC 'About'
   dialogue box.

   Each .CPP file contains a brief description of its contents and
   any work required, but in summary:

      AboutDlg.* - customise to suit (or remove from project)
      AdsApp.*   - edit as described in AdsApp.cpp
      AdsLink.*  - requires no changes
      AdsCmd.*   - requires no changes
      MyCmd.*    - replace with application command function files
      stdafx.*   - requires no changes

   Have fun!

Feedback
   Any improvements, suggestions and, more importantly, bug reports
   are welcomed; please send them to the CompuServe address above.

   One minor limitation known about the main application class is
   that because AutoCAD does not expose its main CWnd object, the
   application has to have its own window (albeit invisible).  This
   means though that when it displays another window, eg. a dialogue
   box, it's possible to 'alt-tab' between the application and AutoCAD
   (although AutoCAD will be in a 'disabled' state until the
   application returns).  I'd be interested to hear from anyone with a
   workaround!
   
   You may also find that the first time the application displays a
   window, it sometimes isn't brought to the top of the window order
   (but after that, it's fine).  If you experience this, you should be
   able to get around it by calling something like:
         MyWnd.SetForegroundWindow();

Acknowledgments
   Some of the concepts used within the CAdsLink class were suggested
   by Bernd Fix, a member of ADGE developer group (hence the copyright
   statement below).  ADGE have their own section within the AutoCAD
   CompuServe forum (GO ACAD) and for more information on the group,
   can be reached via the following contacts:
      Dietmar Rudolph   CIS: 100015,1632
      Beat Fehr         CIS: 100143,613

Disclaimer
   This program is provided "as is" and with all faults.  The author
   specifically disclaims any implied warranty of merchantibility or
   fitness for a particular purpose.  The author does not warrant that
   the operation of the program will be uninterrupted or error-free.

   Portions copyright  1995, Bernd R. Fix. All Rights Reserved.

   Permission to use, copy, modify, and distribute this software in
   object code form for any purpose and without fee is hereby granted,
   provided that the above copyright notice appears in all copies and
   that both that copyright notice and the limited warranty and
   restricted rights notice appear in all supporting documentation. 
