
[ The 3 example source code files are provided with LGUIDES to allow one
to experiment with reading and updating function documentation from
source code.  The files are by Leo Letendre and are part of his moused
Clipper interface functions, used with slight modifications throughout
LGUIDES.  

The following is excerpted from Leo Letendre's MOUSBROW.DOC, the 166 K
doc file for his moused clipper interface functions. Look for the
complete MOUSBROW.DOC in the file MOUSEG.ZIP in the EMS collection. See
LGUIDES.TXT for contact information -Lloyd Standish ]

---------------------------------------------------------------- 

Clipper mouse functions  -  Version 2.0   6/23/93

This package currently consists of code which implements five basic
functions with the inclusion of mouse support for Clipper(tm) 5.01a and 5.2a.
The current functions include the GET/READ system, the database browse  system,
an ACHOICE substitute, a PROMPT/MENU replacement, an ALERT substitute and a
MEMOEDIT function for adding mouse support.

Several basic features which are common to all six will be discussed first.
(Notes about changes since the previous version are at the end of this 
document.)

All six functions include the implementation of mouse "hot spots". These
"hot spots" allow the programmer to designate an area on the screen within 
which a mouse button click will cause the execution of a programmer
designated routine. Several parameters associated with these are
controllable by the  programmer individually or by setting a default value.
These include the minimum delay between repeating the same event and
whether the button must be released prior to returning to the original
routine. These defaults are settable for the entire system. These global
functions are described below.

Following the global functions is a description of each of the main
sections of the package in the order of GET/READ, browse, ACHOICE,
MENU/PROMPT, MEMOEDIT and ALERT. The basis of the mouse implementation is
the set of routines in the Nanforum Toolkit for mouse functions. You will
need that library to use these routines. 

It is wise to initialize the mouse prior to calling any of these routines
even though these routines will do it for you. Calling FT_MINIT during your
program startup will prevent the user from seeing a delay of up to several
seconds which occurs on some machines. (I have seen a 2 second delay on a
Compaq 396/33L and none on a ZEOS 386SX-16). This delay is apparently part
of the PS/2 type mouse system specifications. Subsequent calls to FT_MINIT
do not reset the mouse hardware so the delay will not happen on subsequent
calls to the mouse routines. A new demo has been added which is described 
in DEMO.DOC.

Please direct any questions to:
			Leo Letendre
			CIS: 73607,233

Please report any bugs as there will probably be a few (at least). Also I
am sure there are some oversights in the capabilities. Please pass any
positive or negative comments along. 

A file containing the Norton/Expert Help Guides is available in a seperate
file. On Compuserve, it is called MOUSNG.ZIP. If you obtained this from
some other source, the name could be different. For those of you who have
the Norton/Expert help compilers, I have included a link file for
maintaining your own guides. This will require another program of mine
which is available on Compuserve called FT_DOC.ZIP. It is available in the
same library as the Toolkit and it will extract the appropriate headers and
create the Norton/EH guide for you.

If anyone wishes to use these routines, permission to use the changes to 
Readmodal and the supporting routines, the browse implementation, the
achoice replacement, the menu/prompt, the memoedit function and the ALERT
replacement is granted for use  in any finished program, commercial or
otherwise. However, permission is withheld from those wishing to include
these routines in commercial or shareware libraries.

< text ommitted >
 
Last edited: 6/26/93
