
vxrx20b.zip -- Patches to upgrade VX-REXX from version 2.0a to 2.0b
-------------------------------------------------------------------
 
How to patch VX-REXX version 2.0a to version 2.0b:
 
  0) Backup your existing VXREXX directory.
  1) Copy the ZIP file to the directory where VXREXX is installed
     and make it your current directory.
  2) Unzip the patch file, making sure that your UNZIP program uses
     the directories stored in the ZIP file.
     For example, if you are using UNZIP from InfoZip, use
         unzip -o vxrx20b
     If you are using PKUNZIP from PKWARE, use
         pkunzip -d -o vxrx20b
  3) Your VX-REXX directory will contain a number of new files.
  4) Run the PATCH.CMD file to patch the .EXE, .DLL, and .INF files.
     Your VX-REXX folder WILL be rebuilt.
     Your PROJECTS and SAMPLES directories will not be changed.
     The patch files (with extension .B) will be erased automatically.
  5) VX-REXX 2.0B is now installed and ready-to-go.
     See the revised online "Read Me First" for the list of changes.

Fixes new to 2.0B:
------------------

-- Notebooks no longer cause an access violation on machines running
   OS/2 2.0.
-- The EndEdit event has been re-enabled on containers.
-- Selecting text in the section editor and then displaying the popup
   menu no longer causes an access violation.
-- Popup menus are now displayed over the active window as opposed to
   the window they are defined on.
-- The Slider no longer shrinks unexpectedly.
-- The SpinButton can be switched from a list to a numeric range at 
   run-time using SetStringList.
-- VX-REXX macros now work correctly for message-enabled Presentation
   Manager threads.
-- VRRenameFile now renames directories as well as files.
-- The MultiLineEntryField correctly handles more than 64K of data 
   in the Value property.
-- If you installed the SOM 2.03 toolkit, an incompatibility that was
   introduced with previous versions of the SOM toolkit causes VX-REXX
   programs to go into an endless loop on exit.  This patch includes
   a workaround.  (You may also consider upgrading to SOM 2.04, which
   does not have these problems.)
