README.TXT 

This file contains important information about the Microsoft 
WinPad Preliminary Development Kit. 

I.   Introduction 
II.  Installation Notes and Procedures 
III. Tools 
IV.  Configuration Tips
V.   Release Notes
VI.  Known Problems
VII. Pen Windows 2.0 Support

I.  Introduction 
================

The WinPad PDK contains the components necessary for the 
application developer to build Visual Basic or C applications for 
WinPad. Refer to the PDK documentation for more information about 
the components provided with this PDK.

Note: WinPad communications components are not included in this
release.  In particular, Windows Sockets is not included.

II. Installation Notes and Procedures 
===================================
The WinPad PDK Setup program makes changes to your Microsoft 
Windows system files, installs new Microsoft Windows for Pen 
Computing components, and backs up any previous Visual Basic 
VB.INI files.  An overview of these changes are outlined below. 
Please refer to Chapter 1 of the 'WinPad Installation and 
Application Design Guide' for more information. 

PENWIN and HHSYSTEM
The "drivers=" line in the [boot] section of your SYSTEM.INI file
has been appended to include "penwindows hhsystem".  This loads
PENWIN.DLL and HHSYSTEM.DLL, respectively.  (These two drivers
are also added to the [drivers] section.)  You can remove the
Pen extensions and HHSystem by removing these two words from
the "drivers=" line.  However, if you add them again to this line,
"penwindows" must always precede "hhsystem."

CONFIG CHANGE UTILITY
Existing applications that are compatible with Microsoft Windows 
for Pen Computing version 1.0 will not work with the DLLs required 
for running WinPad. Therefore, you must unload two WinPad DLLs in 
order to use these applications. WinPad Setup installs a utility, 
WPSWITCH.EXE, to allow you to load and unload the WinPad DLL's. 
You can use this utility only if you are running the WinPad 
components as they were set up by the WinPad Setup program. Please 
refer to the section 'WinPad PDK Components' in Chapter 1 of the 
'WinPad Installation and Application Design Guide' for more 
information about Config Change.  

USER.EXE:
In order to enable the WinPad configuration on your Microsoft 
Windows system, you must EXIT Microsoft Windows and run the batch 
file NEWUSER.BAT from your Windows directory. This batch file 
installs a new USER.EXE in your WINDOWS\SYSTEM directory and 
restarts Microsoft Windows.

To restore your original version of USER.EXE, you must EXIT 
Windows and run the batch file OLDUSER.BAT from your 
WINDOWS directory. Please refer to the section 'Changes to 
Files in Windows Directories' in Chapter 1 of the 'WinPad 
Installation and Application Design Guide' for more details on 
switching between versions of USER.EXE.


III.  Tools 
==========
VIDEO DRIVERS:
Several pen-aware video drivers have been provided for your use. 
These can be found in the \BIN subdirectory of your PDK 
installation. You can choose to use these drivers if you want to 
try out inking while working in Windows 3.1.

When running WinPad from the \HHWIN directory, the video driver 
VGAP.DRV is used by default. You should not need to alter this 
default video driver configuration.          


Inking without a Tablet:  
The HHWIN subdirectory is configured to use a mouse as a pen by default.
If you have a digitizing tablet, consult your manual for how to edit
system.ini to use your tablet.

IV. Configuration Tips
======================
CONFIGURING YOUR WACOM PEN TABLET:
You may choose to add a pen driver to the configuration. To do so, you
must modify your SYSTEM.INI file.  Do not run the setup program that comes
with your tablet, as this will overwrite version 2.0 of PENWIN.DLL (which
comes with this PDK) with version 1.0.

To install a WACOM Pen tablet, add the following lines to your 
SYSTEM.INI file:

[Boot]
drivers=pen  (append pen to the list of drivers on this line)

[Drivers]
pen=wacom.drv

[386Enh]
Device=wacom.386 

Depending on your setup, you may also need to add the following
lines:

[Pen Driver]
Wacom510=1 ; if you are using a Wacom 510
Pressure=1 ; if you have a pressure-sensitive pen
Com2=1     ; if your tablet is connected to Com2 port.

To set up for another pen tablet, consult your owners manual.

USING A PEN:
To suppress error messages on startup when running without a pen-
enabled video driver or pen driver, add the following line to the 
SYSTEM.INI file:

[Boot]
PenWinErrors=0


LAUNCHING VB FROM THE WINPAD SHELL:
You can launch Visual Basic from within the WinPad shell 
(HHShell). To do this add the following line to the file 
HHSYS.INI:

  VB Design=<drive>\<WinPad PDK directory>\MWVB\VBMW.EXE

This adds a button to the Shell called 'VB Design' that 
launches Visual Basic.

LAUNCHING APPLICATIONS FROM THE WINPAD SHELL:
To add your application to the WinPad application bar, you can add 
a line to the HHSYS.INI file as follows:

  MyApp=<drive>\<WinPad PDK directory>\MWVB\VBMW.EXE <drive>\<path to MyApp>\MYAPP.MAK

This invokes WinPad Visual Basic with the MyApp project 
loaded. More details are provided in Chapter 2, "Developing a 
WinPad Application," in 'The Visual Basic Programmer's Guide to 
WinPad.'

When you are ready to test your application from within HHShell, 
you can add the following line to HHSYS.INI:
MyApp=<drive>\<path to MYAPP.EXE>\MYAPP.EXE

If you are writing a C application, you must add your application's name
to HHSYS.INI as described above in order to register it with the Application
Manager control.

V.  Release Notes 
================= 
This section describes the release of WinPad that is included with
this PDK, and also describes functionality that will be available
in future releases.

NOTES ABOUT THIS RELEASE
 - Undo and Help are not implemented in most of the applications

 - Drag-and-drop of objects between most applications has not been
   implemented.  System support for this, however, is available.

 - The APIs for using the application manager control from a C
   application currently reside in HHAPPMAN.VBX, not HHSYSTEM.DLL.
   If you are writing a C application, you will need to use
   GetProcAddress.  See the BOUNCE sample in the SAMPLE\BOUNCEB.C
   subdirectory for an example of how to do this.  These APIs will
   move into HHSYSTEM.DLL before WinPad is released.

 - To "Find-enable" your applications objects, add two properties
   to objects that you create: PR_HEADER and PR_MODULENAME.  PR_HEADER
   associates a user-readable header with the object.  Find will only
   search objects which have a header.  PR_MODULENAME should be the
   name of your .EXE.  

   When the Find button in your application is pressed, use the Application
   Manager control to launch the Find application (ModuleName = HHFIND.EXE).
   Find looks at two parameters.  If you supply the entryID of the SOS
   folder that contains your application's objects in the ObjectArg argument,
   Find will search that folder first.  Additionally, strings that you pass
   in the StringArg will be added to the Find drop-down combo box.  You can
   pass multiple strings by separating them with semicolons (;).  For 
   example, "Bill;Clinton" will cause Find to add "Bill" and "Clinton" as
   choices in the combo box.  This enables your application to customize
   Find to make it easy to search for words related to the object being 
   viewed by the user.

   When an object is found, Find will examine its PR_MODULENAME property.
   If found, the user may view the object.  This will launch the application
   named by PR_MODULENAME and pass it the entryID of the object in the
   ObjectArg parameter.  Your application should then display the object.

FEATURES AVAILABLE IN FUTURE RELEASES
The following is a description of product areas that will be
available in future releases of the WinPad development kit.  You
should design your application with these issues in mind.

- Control Controller Control (CCC)
Because WinPad will run in a variety of orientations on a variety
of screen sizes, applications need a method to modify their layout
based on the screen configuration.  The CCC provides a way to set 
up your application to run in a variety of configurations.

- Application Install/Deinstall on WinPad
The details for application installation/deinstallation will be provided
in future PDK releases.

- Object Bitmaps
WinPad will offer the ability to associate a bitmap (icon) with
an object in the Small Object Store.  This will enable applications
such as Find to display a proper icon for objects that it finds.

- Notification Button
Implementation of the notification manager (the blinking exclamation
button in the control bar) is still in progress.

- Help
System-wide help services will be available in a future release of
the WinPad development kit.


VI.  Known problems
===================

If you only see part of your WinPad on screen
  This release of WinPad does not yet support dynamic resizing of the shell
  or application windows.  As a result, the WinPad screen will be clipped 
  when sunning 8514 with large fonts or XGA.

Include Files:
  The PDK does not provide both Visual Basic and C versions of all 
  include files. Check the MWVB\INC and C\INC subdirectories of your 
  PDK installation for include files supplied.

Small Object Store files:
  The Small Object Store (SOS) creates and maintains the files SOS.BIN 
  and SOSI.BIN.  These files are kept in the directory pointed to by 
  the TMP environment variable.  If you have do not have a TMP environment 
  variable, they are kept in the root directory of your hard disk drive.  A 
  sample set of .BIN files are installed for you in this location 
  by WinPad Setup.

  If you need to reinitialize your SOS for any reason:
   1. Quit WinPad, if you are running Windows, or exit WinPad
      if you are running from within HHWIN.
   2. Delete SOS.BIN and SOSI.BIN (if present) from the directory
      pointed to by your TMP environment variable.
   3. Copy *.BIN from the PDK BIN subdirectory to this location.

"An Error Has Occured":
  Periodically you may see this message.  This indicates that a
  VB application has caused a problem.  If you see this, backup your
  SOS BIN files and try reinitializing the SOS, as described in the 
  previous section about SOS files.  This will usually solve the problem.

Removing Applications from the Shell:
  Currently, applications that you add to the shell by modifying HHSYS.INI
  cannot be removed once you've run the shell.  To remove these applications,
  you must reinitialize the SOS as described in the previous section about 
  SOS files.

VII.  Pen Windows 2.0 Support
=============================
A PEN20.DOC (Microsoft Word for Windows format) is provided in the 
\DOC subdirectory of your PDK installation. The same file is 
provided in WinHelp format in the \HELP subdirectory. Refer to 
this file for more information on Microsoft Windows for Pen 
Computing version 2.0. 

WinPad Setup installs the file PENWIN.H. Comments throughout this
file indicate APIs that are modified or not supported in WinPad.
