(Windows 3.1, Windows 95, Windows 98 or Windows NT 4.0 or higher)

If your operating system is Windows 95, Windows 98, or Windows NT 4.0  or higher, download and run

    APLW3015.ZIP

If your operating system is Windows 3.1, download APLW3015.RTP and place it in your APL+Win Version 3 directory and from that directory, from a DOS prompt window, run

    PATCH.EXE APLW3015.RTP

Below is the list of files that will be updated with their new file sizes and dates:
  

 
Note: If after applying the update, you experience problems with running user commands, follow these steps:

1. Use a text editor to edit the file APLW.INI. This file is located in the Windows directory.
   
   
2. Under the [Config] section, set NewUCMDS to 1 and set 'Initial Workspace' to <APL_install_directory>\FIXUCMDS where <APL_install_directory> is the location where APL+Win is installed.
   
   
3. Save the changes and exit the editor.
   
   
4. Start APL+Win then verify user commands are working properly.
   
   

Below is a description of the problems that are corrected in this update.

• REF 868: With the ]WED editor running, invoking the user command, ]FORMS incorrectly gave an error message ("LENGTH ERROR") following the list of forms.
• REF 907: The UNLABELVR function in the UTILITY workspace mistook the :FOR control structure statement as a line label.
• REF 1073: Multiple problem with the user command, ]PCCOPY
• REF 1379: The Resize method on OCX was not triggering onResize event.
• REF 1438: The Draw method's Clear operation to printer was not incrementing page.
• REF 1464: Problem with restoring the focus to ActiveX control.
• REF 1466: Drawing a bitmap to PostScript printers caused a General Protection Fault when the clip region was bigger than the bitmap.
• REF 1476: Setting the size property on some controls ended up with the wrong size.
• REF 1484: Version 5 of Formula One failed to fire its StartEdit event handler.
• REF 1485: A reopened child of a scrolled Picture object was not positioned properly.
• REF 1491: APL crashed with a 328 byte argument to Œlib.
• REF 1492: After changing the origin property for a Picture control, its children no longer scrolled.
• REF 1495: The List's value property mishandled 0 and -1 if set when closed.
• REF 1498: The Listview columndisplay with more than 5 columns were interpreted incorrectly. The system effectively reshaped the argument, using extra columns as the beginning of the next row. The system now ignores columns after column 5. This will allow def variables including columndisplay of more than 5 columns to be ignored.
• REF 1501: The OCX Array properties reported "LENGTH ERROR: Wrong number of arguments".
• REF 1502: ŒLX was incorrectly run for an )XLOAD issued *IMMEDIATELY* after a ŒSA of 'CLEAR' had taken effect.
• REF 1503: When a function name contained the symbol, delta-underbar, multiple problems were visible in the Debugger and session manager.
• REF 1504: The Listview drag scrolling wasn't working if it had exactly one more row than would fit without a scroll bar.
• REF 1506: APL crashed when setting ŒELX to 'ŒERROR ŒDM' and invoking a non-existent user command while waiting on a Form.
• REF 1509: There was a problem with the way the items in a style 5 Listview were highlighted when the Listview lost the focus.
• REF 1512: APL would crash when invoking 'FindNode' 'child' 0 for a Tree.
• REF 1514: In the ADF file, the Windows API ShellExecute was missing the "LIB SHELL32" parameter.
• REF 1516: Opening the Listview with no columndisplay sometimes created two blank column headers.
• REF 1520: Setting column order in columndisplay property for Listview gave wrong order.
• REF 1524: Setting Listview's columndisplay with 5 columns and without Microsoft Internet Explorer 3.0 or later gave DOMAIN ERROR.
• REF 1525: Setting imagesize when bitmap had invalid file gave MEMORY ERROR.
• REF 1526: N {TAKE}[2] 0 should've reported AXIS ERROR, but reported LENGTH ERROR instead.
• REF 1527: 'FindNode' 'child' 0 gave DOMAIN ERROR. This was introduced by fix for 1512, but not enforced prior to that. The system allows 0 to mean either 'root' or 'none', depending on context.
• REF 1528: Error messages from any system command, executed immediately after Œsa„'CLEAR' takes effect, were repeated in the session.
• REF 1529: There was a problem in the interpreter whereby a newly cleared workspace was sometimes already corrupted.
• REF 1532: Invoking )RESET during a pending ŒNI'Recv' operation would possibly lead to a damaged workspace and APL crashing.
• REF 1533: Invoking the user command ]DLLTREE under Windows NT gave a LENGTH ERROR.
• REF 1536: The Copy command sometimes introduced an invisible bodiless function into the target workspace.
• REF 1538: On Windows NT, some APL characters were not displayed correctly in a Listview.
• REF 1542: Setting the size and visible property to 3 for a Form before opening it used the size information for maximized size.
• REF 1543: On Windows NT, a style 1 Listview displayed empty cells using the previous cell's text. We have implemented a workaround in the system to get around this Microsoft bug.
• REF 1546: The documentation for the user command ]PRINT stated that if no data expression were supplied, it would print any tagged region throughout the session manager. This was emoved from the documentation.
• REF 1552: Outer syntax analysis of some functions with 2*14 or more statements were wrong.
• REF 1554: When path names contained '.w3' in the name, the commands in the Load, Xload, Copy, PCopy, Save, Save As, and Drop dialogs failed.
• REF 1555: The Listview painted twice during operations involving the internal routine "InsertRows"; the sortorder and list properties, and the AddRows, InsertRows, and SetRows methods.
• REF 1558: Creating a RichEdit from a def with RichEdit-only style failed with a "ŒWI DOMAIN ERROR: style" error message.
• REF 1559: Invoking SetRows wasn't repainting cells beyond the first column in a Listview control.
• REF 1560: The times-scan function was missing an overflow check.
• REF 1570: When ŒCT was set to zero, both the "match" primitive and the "SELECT/CASE" control failed to match integers to their exact floating point representations.
• REF 1571: When the system is run under Windows 98 with VBX interface support, and APL exits, Windows reported "APLW caused an invalid page fault..." The VBX interface is not supported under Windows 98.
• REF 1575: The runtime interpreter erroneously created a .INI file upon exiting.
• REF 1577: In Windows 98, calling Setup for a Printer created the printer device context with 0 copies.
• REF 1580: Ravel with axis produced an empty PTR result with a NULL prototype causing APL to crash.
• REF 1594: When a component file was tied using the extended file functions and tie number 1, many of the user commands reported a FILE TIE ERROR when run.
• REF 1597: There is a circular reference in the Registry on several keys starting with WScript (under Windows 98) that caused APL to hang when the XInfo method was executed for ALL keys (no filter argument) or when 'W', 'WS', 'WSC', etc. filter argument was explicitly used.