Navigation  without Java Scripts

Problems Solved in Visual Prolog 5.02

Following is a list of problems found in in Visual Prolog, version 5.01, and solved in the version 5.02. Each of the reported problems  receives an ID, a short heading, a description of a problem, and some text under the Version Info entry. There are also a number of small problems solved in the version that are not listed here.

Problems solved in the Compiler
Problems solved in the PROLOG.LIB
Problems solved in the VPI
Problems solved in the VDE
Problems solved in the Linker
Problems solved in the Debugger

Problems Solved in the Compiler

nocopy does not work with single facts

ProblemID: R980506.01 Compiler

Problems Solved in the PROLOG.LIB

Ctrl+Break and Ctrl+C in Win32 text mode should work in the same way as for DOS.

Description:

For DOS text mode programs pressing Ctrl+Break and Ctrl+C will abort the program during run time if  the "Break Check" option in  the "Compiler Options" dialog is enabled.

In the version 5.01 this option can be enabled only for the DOS text mode.

Version Info:

Since v. 5.02 the "Break Check" option can be enabled both for Win32 text mode and DOS text mode. Ctrl+Break and Ctrl+C work in the same way under Win32 and DOS text mode.

Problems Solved in the VDE

Multiprogrammer project is broken when one user adds a control and another adds a module simultaneously.

ProblemID: R980501.01 VDE.PVCS BUG

Some dialogs/windows stored in separate files cannot be imported into other projects from projects created by VDE v.4.0

The problem can arise when the project that had been created by VDE v. 4.0  was converted to the multiprogrammer mode by later versions of the VDE.

Moving of an external file of a resource causes an error

Moving of external files of resources between subdirectories (with replacing of reference to this file in the project). The problem is that an external resource file contains specification of the path where it is placed. And when it is moved manually this path will not be corrected correspondingly.

Open file sometimes leads to the error message 6000

ProblemID: R980423.03 VDE BUG

Problems Solved in the VPI

Leak memory in edit_PasteStr

ProblemID: R980423.01 VPI.Editor BUG
 
After using edit_PasteStr/2 memory was captured until program is ended. Often using this predicate may cause problem.

draw_TextInRect works invalid after a call of draw_Text

ProblemID: R980504.01 VPI BUG

Wrap editor has problems in updating of  an Edit window and sometimes gives GPF in Win16 and in Win32 with BC++ linker.

Problems Solved in the Linker

There is a case when a loader cannot load a 16bit image.

A  loader cannot load a 16bit image created by the PDC Linker. An error message like "Insufficient memory" or "Device is busy" is issued.

Problems Solved in the Debugger

Debugger should give a warning if Source File is newer