Release 1.5A was completed on 03/05/97. The following are enhancements, changes, and fixes that occurred after Release 1.4E was made available.
Enhancements / Changes
Changes were made to assure Year-2000 compliance.
Two variations of the QualifyStamp command were added to the Exclusion menu.
Due to implentation problems on the Windows platforms, support for the following key combinations was eliminated:
Alt-AltLeft
Alt-AltRight
Ctl-CtrlLeft
Ctl-CtrlRight
Shf-ShftLeft
Shf-ShftRight
As such, the Shf-ShftLeft and Shf-ShftRight key assignments were cleared. The ClipRotate command had been assigned to these key combinations.
Fixes
The Locate-type operations issued on a JobList session caused a 1387/0100 error unless that MAXCOL for the session was set to a value <= 253. Fixed.
When BIM-EDIT/XP was unable to load the LU 6.2 DLL, it displayed a message to the effect that it cannot load DLL "APPC.DLL". However, in certain environments, the DLL that was being loaded was WAPPC32.DLL, so the message was misleading. Fixed.
The EditChange command documentation shows that the NSTR operand is required but the command was not requiring it. Fixed to match documentation.
The PutClipboard command failed with a 3824/0100 error when running on the Windows 3.1 platform while the system clipboard was being used. Fixed.
On the Windows platforms, the left Ctrl, Alt, and Shift key (entered alone) assignments were not being recognized. Fixed.
On the Windows platforms, assignments for the following key combinations were not being processed. Fixed.
Alt-CtrlLeft
Alt-CtrlRight
Alt-ShftLeft
Alt-ShftRight
Ctl-AltLeft
Ctl-AltRight
Ctl-ShftLeft
Ctl-ShftRight
Shf-AltLeft
Shf-AltRight
Shf-CtrlLeft
Shf-CtrlRight
If a sync relationship was established between a BIM file and an workstation file while auditing was active, and if auditing was subsequenly set off for the BIM file, when the BIM file was listed or edited, a 0960/0100 error occured. Fixed.
A 0731/0100 error occurred in the iSessionAlter command when a PC was reconfigured to a different screen resolution such that an existing font number was no longer valid. Fixed.
On the Windows platforms, saving of a workstation file did not set the audit line count attribute. This caused the FileLibrary DET and FULL display to show an incorrect audit line count. Fixed.
On the Windows platforms, file attributes were lost during the execution of the FileAuditClear, FileAuditGenerate, or FileAuditRollback commands issued against a workstation file. Fixed.