
				CASE:PM VIP 
			Release Notes, Release 1.10
			              May, 1993

                      L I M I T E D    A V A I L A B I L I T Y    R E L E A S E 

CASE:PM VIP Limited Availability Release is a controlled
release available to existing customers on a request 
basis only.  This release of the product is still in 
test and may still contain some inherent problems.

____________________________________________________________________
CASE:PM VIP Prerequisite Hardware and Software Requirements
____________________________________________________________________

Hardware Requirements

*	An Intel 80386 or 80486 processor or compatible system 
	(an 80486 is highly recommended)

*	Eight Megabytes of RAM (12 megabytes are recommended)

*	A minimum of five megabytes of working disk space for the 
	CASE:PM VIP software and development storage space

*       	An IBM EGA, VGA or compatible monitor

*	A compatible pointing device (mouse, trackball, etc.)

*       	A high density 3.5-inch (1.44M) disk drive


Software Requirements

*	IBM OS/2 2.0, 2.1,  or higher

*	IBM OS/2 2.0 Toolkit

*	IBM C Set/2 Compiler  (for compiling, linking, running, 
	and debugging C language programs on the 32-bit OS/2 
	operating system)

Note:  OS/2 Release 2.0 requires at least 10 Mb. of free disk 
space for the SWAPPER file.  Be sure you have at least 10 Mb. 
free before generating source code in CASE:PM VIP for large
applications.

_______________________________________________________________
Installing CASE:PM VIP
_______________________________________________________________

Refer to the CASE:PM VIP Installation Guide for complete details
on installing CASE:PM VIP, Release 1.0.  The short form version
of the installation is as follows:   From the OS/2 Window or OS/2
Full Screen command line, type:

		 A:SETUP 
and press enter.

________________________________________________________________
Installing More Than One Version of CASE:PM VIP
________________________________________________________________

If you have more than one copy of CASE:PM VIP installed and you 
receive messages such as "can't find *.PNL" or "can't find *.RES" 
object, check your CONFIG.SYS file.  Verify your SETPATH, HELP,
LIB, LIBPATH, and INCLUDE statements are referencing the desired 
version of the CASE:PM VIP directory "first" in the path line. 
Otherwise, CASE:PM VIP will access the DLL files from the 
directory which is located first in sequence in the libpath 
statement.

__________________________________________________________________
Installing CASE:PM VIP and Selecting Automatic Update of 
CONFIG.SYS File
__________________________________________________________________

The CASE:PM VIP installation program will automatically update
your CONFIG.SYS file if you select the automatic update option. 
When the install program updates the CONFIG.SYS file and there
is a path statement or variable in your file which is greater
than 256 characters, you will receive a warning message 
"Waring 401 - String Variable is not large enough for String".
If you receive this message, it is because you have a statement
in your CONFIG.SYS file which is greater than 256 characters
in length.  It is recommended that you manually update your 
CONFIG.SYS file in this situation. 
 
________________________________________________________________
CASE:PM 2.2 to CASE:PM VIP Migration Utility
________________________________________________________________

Customers using CASE:PM 2.2 will be able to migrate their
application to CASE:PM VIP using the 2.2 Migration Utility.  
This utility will convert applications built in CASE:PM 2.2 
to the new object-based modular architecture in CASE:PM VIP.

________________________________________________________________
OS/2 Release 2.1 Support
________________________________________________________________

CASE:PM VIP has been tested under OS/2 Release 2.1.
At this time, no serious problems have been detected.

_________________________________________________________________
National Language Support and Single Byte Character Support
_________________________________________________________________

KASEWORKS is currently developing National Language Support (NLS) 
for CASE:PM VIP.  NLS support for CASE:PM VIP is scheduled for
1993. Support for Single Byte Character Set (SBCS) is currently
available in this release.

__________________________________________________________________
TIPS and TECHNIQUES
__________________________________________________________________

The following sections will provide you with workarounds, tips, 
and techniques for any known problems which exist in this release
of CASE:PM VIP. 
__________________________________________________________________
GENERAL ISSUES
__________________________________________________________________

In the event of a DBL error message, log the message.  Select 
"Ignore" from the error message.  If no other errors occur, save
the object, exit CASE:PM VIP and restart.  If the error persists, 
call KASEWORKS Customer Support Center.      

When generating an application or DLL, the objects(files) are 
not locked. You can continue to prototype the objects as long as
the object is not used by the generator during the code generation
process.

If you ever receive an update to the CASE:PM VIP Knowledgebase
(*.KNB), you must delete the Symbol Table files (*.SMB) associated
with your original Knowledgebase. These Symbol Table files are 
created upon the first generation against a Knowledgebase.

Due to the complexity of the operating system in conjunction
with the CASE:PM VIP product, it is advisable to allow the 
system to complete all screen painting prior to your next 
action. Using the mouse or other pointing device rather than 
keystrokes will alleviate most problems.

CASE:PM VIP may occasionally leave temporary files in your
temp directory.  These files start with a number and can be 
renamed and loaded as you would with any other object.  You may 
want to occasionally clean-up this directory.

Occasionally, you may experience an OS/2 System error, SYS3175
upon the completion of code generation. Ignore this error
message --it will not have an impact on your application.  
KASEWORKS is currently researching this problem in conjunction
with an OS/2 related problem.

CASE:PM VIP will operate on the 8514 monitor displays.  All 
Notebook-like windows will re-size properly.

The CASE:PM VIP Designers are not re-entrant (multiple instances 
active) in this release.  This is managed by CASE:PM VIP through
the Create, Edit, and Find push buttons used throughout the 
product.  These buttons are enabled and disabled controlling 
the availability of each Designer.

__________________________________________________________________
THE CASE:PM VIP SHELL
__________________________________________________________________

If you resize the CASE:PM VIP Shell from the bottom, all
containers within the shell are shifted up. This in effect makes 
the designer container to appear inaccessible.  Open the CASE:PM
VIP shell to full size to view all designers.

Any modification to the View (Icon, Name, Text) of a container 
in the CASE:PM VIP Shell will only exist for the life of that 
session.  The selections are not saved between CASE:PM VIP 
start-up sessions.

The CASE:PM VIP shell system menu and menu bar are only 
accessible via your pointing device (mouse, track-ball, etc.) 
in this release.

As a safe-guard, when you delete a project item or project
folder, only the reference to the project folder is deleted.
The actual file will still exist on your storage media.

The title for a Project is stored in the PROFILE.INI file. 
If this file ever becomes corrupted or deleted, all project 
titles will be lost. Double check your PROFILE.INI file should 
you loose your project titles.

_________________________________________________________________
APPLICATION AND DYNAMIC LINK 
LIBRARY DESIGNERS
_________________________________________________________________


ALT-F4 will not close these designers until they have focus 
in this release of CASE:PM VIP.

The Version String field on the minor tab "Other" under the
major tab "Compile" requires an unquote string.  The system will
automatically add the quotes for you.

It is recommended that you do not use the same Primary Window
also as an unlinked component object when specifying the 
components to be included in an application in the Application 
Designer.   Using the same window as a primary window and as 
an unlinked component may cause generation errors.

_________________________________________________________________
CONTAINER DESIGNER
_________________________________________________________________

Details and Tree views are not available in this release of
CASE:PM VIP. CASE:PM VIP will have support for the additional 
container views in the very near future.

Animation of Containers is limited in this release. Items in
the container are visible, however will not execute during 
the Window animation as they would in a running application. 
To see your container actually execute, be sure to generate,
compile, and then run the application. 

A paint problem with a Container's background is a symptom of 
an insufficient stack.  Increase yourstack size to avoid the 
problem.

A Container recursively linked back to itself is not 
supported in this release.  (Recursive containers).

Extended Code Support for a container control is not 
supported in this release.  Extended Code Support for Container
controls will be addressed in an upcoming Maintenance Release.  
 
____________________________________________________________                                                    
MENU DESIGNER
____________________________________________________________

The panel used to create menu accelerator keys is designed 
for the US. keyboard only.  CASE:PM VIP will have NLS 
(National Language Support) in 1993.  Single Byte Character Set
(SBCS) is available in this release. 
	 
Currently you cannot use system bit maps as menu options.  
Also the bit map "OS2LOGO.BMP" that comes with OS/2 is not
usable -- it cannot be loaded into the Toolkit's Icon Editor. 

The first four letters of the top level pull-down Menu are 
used in the identification of the case statements. This could 
cause duplicate case statements if two top level pull-downs
like "Minute" and "Minus" both had an action item called "Add".

This release of CASE:PM VIP does not support Bit map menu items.

_________________________________________________________________
NOTEBOOK DESIGNER
_________________________________________________________________

All Panels to be used in a Notebook must be created prior to 
entering the Notebook Designer in this release.

None of the Notebook Tabs (Major or Minor) have mnemonics in
this release. If you want to go to the next tab using the 
keyboard, give the notebook tab focus, then use the ALT + 
PageUp/ PageDown key.

Any panels that do not have a title bar, system menu, OK or 
Cancel button will most likely create undesired behavior in the
Notebook. To get out of a Notebook panel while prototyping, which 
does not have a close, system menu, OK or Cancel button, double 
click the left mouse button on the Notebook page.

The font attributes: Outline, Strike-out, and Underline or 
left justified notebook tab text will not animate in this
release.

If you have changed a panel in a Notebook page via the
Panel Designer and the OS/2 2.0 Dialog Editor, be sure to FIND
the panel in order to resave your changes so these are 
accessible in the Notebook Designer.

Extended Code Support for Notebook controls is not supported
in this release.  Extended Code Support for Notebooks will
be supported in an upcoming Maintenance Release.

For generated Notebooks, you cannot re-size the Notebook frame
in this release.  By default, the notebook size is derived by 
the size of its largest panel page.

When setting justification of tab text for a Notebook 
object, each setting is off by one in the actual notebook 
control. Example: if you select "Center" you actually get 
"Right" justification.

________________________________________________________________
PANEL DESIGNER and EXTENDED CODE SUPPORT
________________________________________________________________

There is a limit of twenty-seven (27) characters for a 
Control ID. 

The maximum number of characters for static text in a
Panel is 127 characters.

Presentation parameters set in the dialog editor are not 
used in this release.

Once a panel has been created, if you edit the 
associated dialog editor's resource file (*.RES), you 
must perform a FIND in the Panel Designer to incorporate
your new modifications.  If any Extended Code Support 
(XCS) was previously defined, you will be prompted to
either "migrate" the XCS or "discard" the extended code 
support. 

Extended Code Support (XCS) is not available for either 
Container or Notebook controls on a dialog in this release. 
Although each can be created in their respective designers.

The Value Set Control supports a variable type of 
integer only in this release (no arrays).

The Reset and Default pushbuttons on the Settings page
of the Extended Code Support notebook for Value Sets are 
not working properly in this release.

The Reset and Default pushbuttons on the Properties page
of the Extended Code Support notebook for Pushbuttons are
not working properly in this release.

Modal behavior of Panels are unpredictable when called 
from within a DLL.

____________________________________________________________
PROCESS DESIGNER
____________________________________________________________

If you use the "cut" menu option from the context menu of the 
Process Designer and have only one step object in the Process, 
the only way to "paste" it, is to first add another step.

Because of the nature of some steps in a Process, they cannot 
be animated modal.  Be sure all animated Process steps are 
closed before you continue prototyping.  Example:  
A Window in a process can not be animated modal, because 
it must be able to launch any menu items.

______________________________________________________________
WINDOW DESIGNER
______________________________________________________________

If you close CASE:PM VIP using the OS/2 Task List during Window 
animation, the results are unpredictable (a locked system).  
Close the animated Window before closing CASE:PM VIP.

Container or Notebook objects will not animate when linked as
a client area template. (Panel objects however will animate).

Pointers (cursor) and icons associated with a Window will not 
animate in this release.

The interaction between the Window designer and the Menu 
designer is facilitated by a DBL file "CW234.WIN".  This 
file is sometimes not erased and may be visible in the file 
picker.  Ignore the file.

Support for scroll bars settings such as range or initial 
position are not generated in this release.

This release does not support the animation of windows linked 
to User Defined Code objects.  You may receive a generate error 
if you have previously tried to animate the User Defined Code 
object.  If you receive a generate error, close CASE:PM VIP, 
reopen it, and then perform the generation.

_________________________________________________________________
ON-LINE HELP FACILITY
_________________________________________________________________

"Field level" help is available for all dialogs. Only
"page level" help is available for dialogs which are contained
in a Notebook in this release.

No help is available for Template controls in this release.

_________________________________________________________________
OTHER INFORMATION
_________________________________________________________________

If you specify a Product Information Panel without turning
on help support, the code will be generated for the panel, 
but it is the user's responsibility to call that panel via 
an added menu option.

When a field utilizes a user mask, such as (999) 999-9999, 
the data entered as well as the mask, are stored in the 
variable.
	
A users include files are not part of the dependency 
list in the make file (*.MAK).

In the event you receive a generation error "Unable to open
FILENAME.EXT", this is commonly caused by a recursive link 
(an object linked in more than one place).  Remove the 
recursive link and try to generate the application again.
 
The validation routines provided in the CWVALID DLL 
require a "mouse click" to accept any error message boxes. 
Using the "Enter key" produces unpredictable results. 

This release of CASE:PM VIP does not support messages 
for the Spin Button and Slider controls.

The 0/Ins key of the numeric key pad does not work for 
Entry Fields prototyped with User Mask validation.

It is recommended that you do not install CASE:PM VIP on 
a network in this release.  CASE:PM VIP application objects
may be located on network drive in this release. 

Entry Fields prototyped with Date, Currency, or User 
Mask validation do not properly check for required field
status upon acceptance of the dialog or window.

When running or executing a container (linked to a menu 
item) which contains another program or executable,
if you receive an error message that it cannot find your
executable (or an Error Code 2), be sure to reference
the .EXE location in your LIBPATH and SET PATH 
statements in the OS/2 CONFIG.SYS file. For example, 
if the executable is located in the CASEPMVP\QUIKTOUR 
directory, 

the LIBPATH and SET PATH statements should be 
referenced as follows in the CONFIG.SYS file:

	LIBPATH=.;C:\CASEPMVP\QUIKTOUR
	SET PATH=.;C:\CASEPMVP\QUIKTOUR

Be sure to reboot your system after changing the 
CONFIG.SYS file.



For additional support on CASE:PM VIP, Contact
KASEWORKS' Customer Support Center at (800) 925-8990
or use KASEWORKS bulletin board at (404) 417-3265






