Navigation  without Java Scripts

Visual Prolog Packages and Examples Problems 

PDC's Document Handling Package
Report and  Own_Draw Packages
Tree Package
TreeBrowser Package
SOCKBIND
Directory Browser
Dialog Package
GRID Package
Examples

DOC_TOOL

Outdated Description of the  Document Handling Package in the Visual Prolog 5.1 Help 

R990217.03:    FIX

The topic "How to Include the Document Handling Package into a Project" includes incorrect recommendation to include  YYWRAP.PRE and YYWRAP.PRO files into a project. These files do not exist.

According to the Visual Prolog 5.1 Help topic concerning the DOC domain, the DOC_FLOW_ELEMENT can still assume a value called "lang". It says so even though "lang" has been removed from the DOCSTR.DOM file. In DOCSTR.DOM there's a comment explaining that it has been removed due to the fact that it has become obsolete.

On the other hand, the following domains are missing from the VIP Help file about the DOC domain: OPTION_LIST & DOC_OPTION, PARAMLIST & PARAM, FRAMELIST & FRAME. These are all included in the DOCSTR.DOM file.

Version Info

The information applies to  Visual Prolog 5.1 and previous versions. 
The information has been updated in Visual Prolog 5.2.

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.

Version Info

The information applies to  Visual Prolog 5.2 and previous versions. 

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.

Bug in the HTML Parser error handling

R990217.01

HTML Parser reports wrong line and position numbers.

Version Info

The information applies to  Visual Prolog 5.1, build 564, and previous versions.
Fixed in Visual Prolog 5.2.

Report and  Own_Draw Packages

Incompatibility of the Report and the Own_Draw packages in one module

The problem of incompatibility of the Report and the Own_Draw packages is  caused by intersecting names.

Version Info

The information applies to  Visual Prolog 5.1, build 564, and previous versions.

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

Version Info

The information applies to Visual Prolog 5.1, build 565. See Upgrade Notes.

Tree Package

Runtime error while printing big trees

Runtime overflow error in the internal Tree package procedure of  page size calculating for printing  trees in 16 bit applications.

Version Info

The information applies to the versions 5.01 and 5.02 only. The problem is solved in Visual Prolog 5.1

Bug in a big tree display

If a tree width or height exceeds 32767 pixels, the tree is not displayed properly:

Under OS/2 it is impossible to scroll a big tree.
Under Windows, one cannot use a thumb for scrolling. However, it is possible to scroll using scroll-bar direction arrows.
Version Info

The information applies to  Visual Prolog 5.1, build 564, and previous versions.

The Print Status dialog determines a number of a printing page for a Project tree incorrectly

Version Info

The information applies to  Visual Prolog 5.1, build 564, and previous versions.

TreeBrowser Package

512 error while building a project including the TreeBrowser package 

The 512 Type error: "Wrong object type" is generated, while building a project including the TreeBrowser package.

Workaround
  1. Copy PLUS.ICO and MINUS.ICO files from VPI\ICLUDE\TREEBRWS into your project's RES\WIN subdirectory. 
  2.  Using the Project window's "Icon" button add these icons to your project. To add these icons press the "New" button. The  Icon Attributes dialog will be invoked.
  3. Using the "Browse" button" in the  Icon Attributes dialog:
Show the path to an appropriate icon.
Specify a name of the image that will appear in the list of the Project window ("plus" or "minus").
Specify a constant that is used to identify the image in your program.  
You can either input it directly from the keyboard or allow the VDE to create a default value. 
The default values for icon constants are: idi_<icon name>. 
  1. Click on the "Modules" button of the Project window. Select VPITOOLS.PRO. Double-click. 
  2. In the VPITOOLS.PRO after IFDEF use_treebrowser add: 
    include "<your_project_name>.con"
  3. Build a project.
Version Info

The information applies to  all versions of Visual Prolog.

SOCKBIND

Previous versions of the FTPAgent are incompatible with Visual Prolog 5.1
FTPAgent issues an extra FTP command
The FTPAgent Main Window is distorted when large fonts are set.
The ..\SOCKBIND\SOURCE directory is missed in the WEB version of Visual Prolog 5.1 Personal Edition

Previous versions of the FTPAgent are incompatible with 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
Version Info

The information applies to  Visual Prolog 5.1, build 564, 565.

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

R990216.04

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.

Version Info

The information applies to  Visual Prolog 5.1 and previous versions. 
Fixed in Visual Prolog 5.2.

The FTPAgent Main Window is distorted when large fonts are set.

The FTPAgent Main Window is distorted when high resolution and large fonts are set in the Display Properties.

Version Info

The information applies to  Visual Prolog 5.1, build 564, and previous versions.

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.

Directory Browser

Directory browser does not work with a network path under Win16

R990222.01

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

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.

Version Info

The information applies to  Visual Prolog 5.1, build 564, and previous versions.

Workaround
  1. Beginning from  Visual Prolog 5.1 (build 565) it is possible to use tabdlg_SetState predicate. This predicate correctly handles controls in inactive sheets.
  2. To set Enabled/Disabled and Visible/Invisible flags in the 564 build, a programmer can use the following event coming in the moment of activating of the sheet including the control:
    e_User (SheetId, SheetState)
    State
    Value
    Active 1
    Inactive 0

GRID Package

If a programmer checks the type of data that is allowed for a certain column, an  error occurs in an application in the case, when type-checking fails and the maximum allowed input length for a column is reached. In this case, the error message does not disappear after pressing "OK".

Version Info

The information applies to  Visual Prolog 5.1, build and previous versions.

Fixed in Visual Prolog 5.2.

Examples

Visual Prolog 5.1  is not fully compatible with some examples from Visual Prolog 5.02
The WEB version of ESTA and other ISAPI examples from the Personal Edition hang a server
The WEB version of ESTA example does not work properly under Netscape Navigator
Problem with 16-bit examples under 32-bit VDE

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

Read Upgrade Notes.

Version Info

The information applies to  Visual Prolog 5.1

Problem with 16-bit examples under 32-bit VDE

One cannot open 16-bit examples from the 32-bit VDE.

Version Info

The information applies to  Visual Prolog 5.1, build 564 and previous versions.

More information
Beginning with Visual Prolog 5.1, build 565, the problem does not exist, because .VPR files in the examples from WINBIND and TXTEXAMP directories have been replaced with the .PRJ files.
Workaround
Use VPICONV to convert .VPR files in the build 564.

The WEB version of ESTA example does not work properly under Netscape Navigator.  

Under Netscape Navigator 4 pressing the "Load" button causes the "Save As" dialog instead of running a program.

Version Info

The information applies to  Visual Prolog 5.1.

Fixed in Visual Prolog 5.2.

The WEB version of ESTA and other ISAPI examples from the Personal Edition hang a server

R000229.001

The WEB version of ESTA and other ISAPI examples from the Personal Edition hang and crash a server.
The "depth of hanging" depends on a WEB server and operating system. 
For example, if the Internet Information Server under Windows NT 4.0 is used, these applications hang the sever. It is impossible to run any other WEB applications in this case.  

If the Personal WEB server  is used under Windows 2000, the ISAPI application is hanged and cannot be killed. Visual Prolog cannot rebuild this application. Other web application can run normally.

Workaround

Users of the Personal Edition can try the ESTA expert system shell directly from the WEB.

To run Visual Prolog ISAPI applications, it is necessary to use the Professional version of Visual Prolog.

Version Info

The information applies only to the Personal Editions of Visual Prolog 5.1 and 5.2. 
The problem does not exist in Visual Prolog Professional Editions.

See also:

Known Problems  Upgrade Notes | Patches | Technical Notes | Support_FAQ