home *** CD-ROM | disk | FTP | other *** search
- Four problems were encountered when testing a prerelease version of
- Visual Basic 5.0. These problems are summarized here so you will
- recognize them if you encounter them yourself.
-
- 1. (Chapter 1) If you omit color, Visual basic's PSet routine should
- use the color specified by the ForeColor property of the form or
- picture box drawing the point. In the prerelease version of Visual
- Basic 5.0, PSet ignored ForeColor and set the point in black. If you
- have this problem, try explicitly telling PSet what color to use.
-
- 2. (Chapter 3) In Visual Basic 4.0 the Printer's ForeColor property
- defaults to &H80000008. This produces a solid black line. In the
- prerelease version of Visual Basic 5.0, ForeColor defaulted to 0. This
- produced a broken line made up of dots (though the value 0 draws a
- solid line in Visual Basic 4.0). If you have this problem, explicitly
- set the Printer object's ForeColor to &H80000008.
-
- 3. (Chapter 3) Visual Basic 5.0 makes some changes to color palettes.
- In the prerelease version palettes did not always behave as expected.
- In example program RGBCOLOR, the middle picture box managed to use
- colors defined by the third picture box even though they were not
- defined in its color palette.
-
- 4. (Chapter 3) Example program PALEDIT also had palette problems in
- the prerelease version. Due to complications in using PC_EXPLICIT
- palette entries, the colors displayed do not correctly match the
- system entries.
-