Navigation  without Java Scripts

Known Problems with Visual Prolog Packages and Examples

Known Problems with the PDC's Document Handling Package
Known Problems with the Report Package
Known Problems with SOCKBIND
Known Problems with the Directory Browser
Known Problems with the Dialog Package
Known Problems with Examples

Known Problems with DOC_TOOL

The .RTF parser bug in using colored fonts

There is a little bug: if a colored phrase in an .RTF document is followed by a table (right after), this table is colored as well.

Workaround: add any uncolored char (a single blank) just after a colored phrase.

Loosing of special  characters  embedded in the RTF while RTF -> DOC -> HTM conversion.

The problem with special charactares is a known problem in the MS Word. Word stores special RTF tokens for these characters, which  both DOC_TOOL and any Microsoft Windows Help Compiler cannot process.

Workaround:

In order to avoid this problem, format the character with the Symbol font (without using Insert | Symbol command). This is the only way to make DOC_TOOL  correctly process special characters.

Known Problems with Report Package

Incompatibility of the Report package with examples and applications created by previous versions of Visual Prolog

See Upgrade Notes.

Known Problems with SOCKBIND

Previous versions of the FTPAgent are incompatible Visual Prolog 5.1

The incompatibility is due to the fact that an additional parameter has been added to an alternative error of the FTPlayer domain ftplay_reply (\SOCKBIND\INCLUDE\FTPLAYER\FTPLAYER.DOM).

The following error is generated while compiling:

E:SOCK_TR.pro, Pos:5125, 507
Workaround

To avoid the compiling error while building old examples with  Visual Prolog 5.1, downloaded from WEB, a user should add an argument to this alternative in a source code. To do this, it is necessary to replace:

scan_process_answer(S,error(ErrStr)):-

with

scan_process_answer(S,error(_ErrNumber, ErrStr)):-

FTPAgent issues an extra FTP command

If the option "Do Full Synchronization" is turned on, an old version of a file is deleted at a target site before transferring of a new version, instead of simple transferring of a new file version without a delete operation. The described problem does not influence the results of synchronization.

The ..\SOCKBIND\SOURCE directory is missed in the WEB version of Visual Prolog 5.1 Personal Edition.

It is impossible to compile projects and examples that use SOCKBIND (eg. WEBAGENT), because the ..\Sockbind\Source directory is missed.

Workaround

Download the Source.zip (18 KB)

Version Info

The information applies to the WEB version of Visual Prolog 5.1 Personal Edition.

Known Problems with the Directory Browser

Directory Browser does not work with a network path under Win16

The Directory browser uses disk predicate that does not support the network path under Win16.

Known Problems with the Dialog Package

A problem with setting Enabled/Disabled and Visible/Invisible flags for controls in inactive sheets.

Using of a standard VPI predicate win_SetState  or a Dialog package predicate dialog_SetState for setting Enabled/Disabled and Visible/Invisible flags for controls in inactive sheets does not lead to the expected result.

Workaround

In Visual Prolog 5.1,build 565 it is possible to use a new tabdlg_SetState predicate. This predicate correctly handles controls in inactive sheets.

Known Problems with Examples

Visual Prolog 5.1  is not fully compatible with some examples from Visual Prolog 5.02

Read Upgrade Notes.

See also:

Known Problems in the Build 565 | Solved Problems | Upgrade Notes | Patches | Technical Notes | Support_FAQ