APL2000

APL+Win Version 9.0

Introducing APL+Win Version 9.0. Visionary yet practical, the single comprehensive development tool for creating the next generation of applications has arrived. Developers can use APL+Win to create powerful applications quickly and effectively.

APL+Win has been continuously developed and advanced for over 30 years, making it the most robust and reliable development environment available. It provides a stand alone application development environment and with APLNext WebServices, integration with the Web browser and Web services.

The APL2000 Subscription Program is designed to help customers to successfully develop, deploy, and manage systems built around a broad range of high-quality APL2000 solutions for the server and the desktop. This program provides a comprehensive, annual service contract that covers all APL2000 products at use within the customers enterprise. It also provides a managed support relationship for customers who have made a significant investment in APL2000 technologies. Pricing varies by subscription level.

This version contains the following modifications:

New [Compatibility]UseVBPrefix startup options

New support for programmatically unloading a multi-threaded DLL or ActiveX object from memory

Bug Fixes

New [Compatibility]UseVBPrefix startup options

The purpose of this was to better support the VB and X prefixes in properties, methods and event handlers.

New Options:

Value	Description
2	Use VB or X prefix (with VB prefix reported by properties, methods, events)
3	Use X or VB prefix (with X prefix reported by properties, methods, events)

New support for programmatically unloading a multi-threaded DLL or ActiveX control from memory

Support for unloading a multi-threaded DLL or ActiveX control from memory after having been used by Œwcall, Œna, or Œwi.

To unload a multi-threaded DLL or ActiveX DLL, perform steps 1-4 below:
(Note: Steps 1-3 are only required for a single-threaded DLL or ActiveX control.)

1. )RESET

   This will make sure the SI stack is unwound in order that the next 
command can run to completion. 

Note: You may skip this step when there is no suspension in the stack.

2. object Œwi 'Delete'

   This releases the ActiveX control loaded by APL+Win.

   Note: '#' Œwi 'Reset' may also be used to 
relese all ActiveX objects.

3. Œwcall 'W_Reset'

   This will immediately unload a single-threaded DLL or ActiveX control 
and mark for unloading a multi-threaded DLL or ActiveX control.

   There is also a new built-in W_ResetUnload function that takes 
an argument specifying the delay (in milliseconds).

   Œwcall 'W_ResetUnload' delay
	 
	 If you call it with a 0 delay then the DLL will be unloaded immediately 
without delay.

   Note: If you call W_Reset rather than W_ResetUnload the 
default delay is 1000 milliseconds.

4. Œwcall 'W_Reset'

   This step is necessary when unloading a multi-threaded DLL or ActiveX 
object. This must be called at least 1000 milliseconds after the first 
W_Reset call.

   You can forgo this second W_Reset call if (1) all ActiveX objects 
are single-threaded or (2) you call W_ResetUnload with delay=0.

   NOTE CAREFULLY: In the above sequence you MUST delete the ActiveX control 
before calling W_Reset. Otherwise the ActiveX dlls will not be 
available for unloading and will NOT be marked for unloading (so the second 
W_Reset call will not unload the DLL even if it is done after the 
specified delay period).

Bug Fixes

Interpreter

In versions 6.0 to 8.3, executing ŒERROR ŒDM did not correctly clear the stack after a suspension during the execution of a function.
Invoking the Run(Resume)-F5 menu option in Code Walker didn't resume execution of the suspended function and instead gave a SYNTAX ERROR.

Session

High-order character arrays that were items in a nested array did not appear correctly in the session.

APL GUI

The onMouseDouble event handler was visible but not operational for the DateTime, MDIForm, Progress, Spinner and Trackbar controls. Research revealed that this event handler was unsupported by these controls so the event handler was removed for them.
In versions 6.4 to 8.3, clicking the Option control with the mouse in a Form with an ActiveX control caused APL+Win to become unresponsive.
In version 8.3, ŒWARG reported the size of the Form including the size of the Status bar or CommandBar controls during the Form's resize event.
The Unicode text did not appear correctly in a Listview control that was a child of the Frame control.

APL Grid

Assigning the xMissing property value for a cell to 0 cleared the cell of its data and also changed the value for the xMissing property for the cell.
In versions 7.1 to 8.3 of the APL Grid, extraneous onXEditEnd events fired with multiple cells selected in the grid.
In prior versions of the APL Grid, the onXKeyMove event handler fired before the onXEditEnd event handler. This gave the appearance that the active cell was changing but then it never did if validation failed during the onXEditEnd event. It was necessary to fix this bug in order to fix the bug reported in the onXEditEnd event handler.
In prior versions of the APL Grid, when validation was set for a cell, double clicking the left or right mouse button on a different cell when a cell was being edited caused the invalid cell's value to be discarded.

Miscellaneous

The TEXTREPL and WORDREPL functions in the ASMFNS.W3 workspace would run in an infinite loop.

Note: The APL+Win 9.0 update requires you to have APL+Win 8 installed on your machine.

System Requirements for APL+Win Version 9.x

Requirements vary for different combinations of components within APL+Win Version 9.x. Review the table below to determine the minimum system requirements for running APL+Win Version 9.x

Processor	450-megahertz (MHz) Pentium II-class processor (600-MHz Pentium III-class processor recommended)
Operating System	APL+Win Version 9.x can be installed onto any of the following systems: Windows 7 Windows Vista Windows Server 2003 Windows XP Windows 2000
Memory	Windows Vista: 1 GB of RAM Windows Server 2003: 512 MB of RAM Windows XP: 512 MB of RAM Windows 2000: 512 MB of RAM
Hard Disk	60 MB of available space required on installation drive

Site Map