PowerBASIC 10.0 for Windows

[Bob Zale]

CONTROL GET CLIENT and DIALOG GET CLIENT can generate a serious error (GPF) if executed with an invalid handle. This will be updated in 10.01.

If you are using this code to see if a window still exists, you might find the ISWIN() function to be a better choice.

[Bob Zale]

PowerBASIC 10.0 for Windows

The EOF() function may not always recognize a soft eof character (&H1A) in a sequential file opened for INPUT. This will be updated in 10.01.

[Bob Zale]

PowerBASIC 10.0 for Windows

In the PowerTime class, the TimeDiff method was mis-documented. The compiler and the documentation will be updated in 10.01. Please refrain from any use of this method until the update is released.

[Bob Zale]

PowerBASIC 10.0 for Windows

The LPRINT ATTACH statement will fail due to an internal character mode mismatch. This will be corrected in version 10.01. As a temporary workaround, you can pass the printer port name as an ANSI string with a UCODE$() override. Only this precise combination will be effective.

LP$ = "LPT1"
LPRINT ATTACH UCODE$(LP$)

You will have to reverse this change for use with version 10.01.

[Bob Zale]

PowerBASIC 10.0 for Windows

The REPLACE and REPLACE ANY statements fail when used with Wide Unicode parameters. This will be corrected in version 10.01.

[Bob Zale]

PowerBASIC 10.0 for Windows

In the WinAPI file DDT.INC, %CBN_SELENDCANCEL is incorrectly defined. Please change it to:

%CBN_SELENDCANCEL = 10

[Bob Zale]

PowerBASIC 10.0 for Windows

The StringBuilderA.Insert Method can produce an incorrect result with certain data and index positions. It will be corrected in version 10.04.

The StringBuilderW.Insert Method functions correctly.

[Bob Zale]

PowerBASIC 10.0 for Windows

The IPowerTime interface cannot be inherited accurately. This will be corrected in the free update to version 10.04.

[Bob Zale]

PowerBASIC 10.0 for Windows

The XPRINT SET CLIP statement can fail if it is not preceded by an XPRINT statement. This will be corrected in the update to 10.04.

A workaround is to insert XPRINT " " before the XPRINT SET CLIP.