KASE:Set (tm) Release Notes                                     Version 2.1
___________________________________________________________________

This document addresses issues with the KASE:Set product that surfaced 
too late to make it into our documentation.  These issues include:

Installation Program

    Always delete KASE:Set with the supplied Installation and Maintenance
    utility.  It will delete all files created by the installation program,
    including those maintained by the installation program (IBM Software 
    Installer).  If you manually delete the KASE:Set directory and try to
    reinstall KASE:Set, it will display an error message about the product
    not being installed.  To rectify this problem:

        - Edit the file x:\os2\system\epfihcnf.cnf
        - Delete any line(s) referencing the KASE:Set product
        - Save the file
        - Restart the installation program

    Note that these steps are only necessary if you manually delete
    KASE:Set.  If you use the installation and maintenance utility to 
    delete the product, you can reinstall at any time.
    
Starting  KASE:Set from the KASE:Set Folder

    KASE:Set is well integrated with both WorkFrame/2 version 1.1 and 
    version 2.1.  The program is meant to be launched from the WorkFrame/2
    environment.  If you'd rather start KASE:Set from the WorkPlace shell
    use the KASE:Set icon in the KASEWORKS KASE:Set folder.  The icon is
    created initially to start in the QuikTour directory.  If you want to 
    start it in another project directory, open the program object's settings
    view, and change the parameters for the program from:
    
        /O X:\KASESET\QUIKTOUR /F %*

    to

        /O Z:\PROJDIR /F %*

    Where Z:\PROJDIR is the project's directory.

KASE:Set and WorkFrame/2 Version 2.1

The installation program adds KASE:Set as an action in the default actions
profile.  However, since there is no option to change an action's startup
directory, the KASE:Set directory must appear in the PATH and LIBPATH before
any other KASEWORKS product directories.

KASE:Set and WorkFrame/2 Version 1.1

If you delete KASE:Set with the installation and maintenance utility, you 
must manually delete KASE:Set from the tools menu.

__________________________________________________________
|                                                                            |
| CLARIFICATION, TECHNIQUES, KNOWN PROBLEMS & WORKAROUNDS |
|_________________________________________________________|

Using Program Objects:

    Program objects that allow you to link to an executable can only be
    internalized.

Animation:

    Animating a window with a notebook client area template does not 
    animate the notebook control.

    Reiterative animation of the same window within the same KASE:Set
    design session may be unstable.

    There is a known problem with animating an application that contains
    a PNL object that has icons.  All components will animate correctly
    but, the icon controls will not appear.

Notebook Client Area Templates:

    The notebook client area template selection panel does not allow
    viewing a notebook directly.  To view a notebook, use the notebook
    designer.    

Dialog Templates vs. Canvases

    The KASE:Set User Interface Class Library knowledgebase generates no
    dialog templates for panel objects.  Instead, panel classes are derived
    from ICanvas.

User Interface Class Library knowledgebase:

    The knowledgebase does not support duplicate control identifiers on a 
    single dialog, except for static controls (static text, icon, and bitmap 
    controls) and group boxes using the dialog editor's UNUSED identifier.

    Notebook pages and windows are constructed when a notebook object is
    constructed.  Dynamic loading of notebook pages is not implemented.

    The User Interface Class Library doesn't support value set controls;
    no code is generated for value sets.  Value sets are supported in the
    C knowledgebase.

    Ok and Cancel buttons on notebook pages are not supported.  If you place
    an Ok or Cancel button on a panel that is placed on a notebook page, 
    generated programs will terminate with a protection violation. It should be
    noted that it is a CUA violation to have these controls on notebook pages.

    Changing the font for a control or notebook may cause general protection
    faults on some machines.  According to IBM, this may be a combination of
    display driver and video problems.  The workaround is to defer to the system
    default font.
 
    Notebooks used as Client Area Templates (CATs) may have their very topmost
    section truncated by the caption or menu bar.  The workaround is to modify
    the underlying resource to allow more room between the dialog frame and the
    topmost row of controls.

    Accelerators (Shift-Home and Shift-F3) do not work.
 
    
