/****************************************************************************
 File: readme.txt

 (C) Copyright 1992 by GO Corporation, All Rights Reserved.

 $Revision:   1.5  $
   $Author:   kcatlin  $
     $Date:   31 Jan 1992 08:25:06  $

 Inputapp is a simple application that demonstrates pen-based input
 event handling. As the user drags the pen around, inputapp draws 
 a small square in the window. To provide this functionality, it 
 creates a descendant of clsWin (clsInWin), which looks for pen 
 input events.

 Inputapp's window tracks the pen by drawing a small box at the xy
 location provided by the event. It also erases the previous box by
 first setting its DC's raster op to sysDcRopXOR. Then it redraws
 the box at the previous location, thereby erasing it.

 Note: If you want your windows to respond to gestures or handwriting,
 you usually do not look for input events yourself. Instead, you use
 specialized window classes such as clsGWin and clsIP, which "hide"
 low-level input event processing from their descendants. These
 classes send higher-level notifications such as msgGWinGesture 
 and msgIPDataAvailable.

****************************************************************************/

/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 *								Objectives					  			   *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
/*
 This sample application shows how to:
	-:	create a drawing context in a window
	-:	set a window's input flags to get pen tip & move events
	-:	handle pen events (PenUp, PenDown, etc.) in a window
	-:	use BeginPaint/EndPaint messages
	-:	turn on message tracing for a class.
*/

/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 *								Class Overview	  						   *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
/*
 Inputapp defines two classes: clsInputApp and clsInWin.
 It makes use of the following classes:

	clsApp
	clsAppMgr
	clsClass
	clsSysDrwCtx
	clsWin

 The only function of clsInputApp is to create clsInWin as its client 
 window. It does this in its msgAppInit handler.

 clsInWin is a descendant of clsWin. Because clsWin does not turn on any
 window input flags, clsInWin must set window flags to get certain pen
 events. 

 Since clsInputApp recreates the input window from scratch and has no other
 instance data, it does not need to file itself. The input window does not
 need to save state either. When called upon to restore its state 
 (msgRestore), it simply reinitializes.
*/

/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 *									Files Used	  						   *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
/* 
 The code for inputapp is in \PENPOINT\SDK\SAMPLE\INPUTAPP. The files are:

	INPUTAPP.C:		the source code for the inputapp classes
	METHODS.TBL:		the method tables for the classes.
*/ 

/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 *								Compiling	  							   *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
/* 
 To compile inputapp, just 
	cd \penpoint\sdk\sample\inputapp
	wmake
 This compiles the application, and creates INPUTAPP.EXE in 
 \PENPOINT\APP\INPUTAPP.
*/

/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 *								Running	  								   *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
/* 
 After compiling inputapp, you can run it by
	1) Adding \\boot\penpoint\app\Input Application to \PENPOINT\BOOT\APP.INI
    2) Booting PenPoint
	3) Creating a new inputapp document, and turning to it.
 Alternatively, you can boot PenPoint and then install Input Application
 via the Connections Notebook.
*/
