November 3, 1998

Dear OKScript user,

The OKScript Status Report is sent to OKScript licensees, 
developers and friends when significant updates have been
made to the program. To be removed from the distribution 
list please reply to this message and indicate that desire.

Most of the OKScript developments that have occured
during this period involve refinements to the functionality of
a few instructions that are primarily used in complex scripts,
support for international character sets/keyboards, and a few 
bug fixes.

If these issues affect your scripts you can download the 
latest revision from http://home1.gte.net/yweare. Your existing 
license will automatically be active on the new software if you
install it to the same directory, otherwise you will have to 
re-enter the registration data (or copy the okscript.ini file from 
the folder where your licensed program was installed.) The 
current build is dated November 3. Click Help | About to determine 
the date of your copy of OKScript. 

This list is ordered by the (approximate) significance of the issue. See
the help file to learn more about new capabilities.

1. Anomalies with the DELAY, CALL and FINISH instructions
   and the Abort_Script! menu (which only appears after a script
   has been executing for a few seconds) were corrected.

2. Support for multi-line commands was added with the
   MORE instruction. For example, if you have a long
   message to display in a message box you might recode
   it something like this:

   MESSAGE bla bla
      MORE bla bla
      MORE bla bla

3. Most diacritic characters are now supported. If you are an
   international keyboard user please let me know if you have 
   problems with your particular keyboard.

4. Support for editing very large scripts was added to the 32 bit
   version. See Script | Options for settings.

5. Support for enabling and disabling panel elements (buttons
   and menus) was added via the MODE instruction. With this
   came the need to test the current state of an element so
   two new iftypes were added - IF BUTTON and IF MENU. These
   features provide an alternative to plagiarize for quickly producing
   custom panels for pickup partnerships. Dave Miller (okb://dbmiller) is
   building a framework for this capability.

6. The USE instruction was added. USE allows a script
   to reference a collection of PROCs and MACROs in a
   separate file. This is useful if you have many scripts that
   all use a common collection of support code.

7. Now you can force the loading of a script file (from a script)
   even if it is already loaded in an editor page. Just prefix the 
   filename in the OPEN instruction with an asterisk, e.g. 
   OPEN *script.oks and the script.oks from disk will replace the 
   script.oks that is already there. If script.oks is the currently 
   running script its panel will be rebuilt. This is useful for scripts
   that modify themselves or other scripts.

8. The full pathname of the current panel's file can now be 
   retrieved with the predefined macro %-panel%

9. The odd behavior that occured when a script issued
   a CLOSE instruction and there was no other panel script
   to transfer to was fixed - OKScript now returns to editor mode.

Your ideas and problem reports *are* appreciated. You can email 
them to me or post them to the message board that I have set
up at my web site. Thank you for using OKScript. 

Michael Mardesich
okb://mikezzz