The information in this article applies to:
- Standard, Professional, and Enterprise Editions of Microsoft Visual
Basic, 16-bit and 32-bit, for Windows, version 4.0
SYMPTOMS
Although both the 16- and 32-bit versions of the Gauge OCX allow you to
specify a 256-color bitmap for the Picture property, in many cases this
bitmap is not displayed correctly.
STATUS
Microsoft has confirmed this to be an issue in the Microsoft products
listed at the beginning of the article. We are researching this problem
and will post
new information here in the Microsoft Knowledge Base as it becomes
available.
MORE INFORMATION
This problem also occurs when running a video driver with a color depth of
more than 256 colors.
Steps to Reproduce
- Start Visual Basic, or if it is already running, choose New Project from
the File menu.
- If the Gauge OCX is not in the Toolbox, right click on the Toolbox and
select 'Custom Controls' from the pop-up menu. In the Custom Controls
dialog box, double click on the entry labeled 'MicroHelp Gauge Control'
and click OK to add the Gauge control.
- Click and drag a new Gauge control onto the form.
- Double click on the gauge's Picture property and set it to a 256 color
bitmap. With Windows 3.x or Windows NT, a bitmap called 256color.bmp
exists in the Windows directory. No corresponding 256 color bitmap
comes with Windows 95; however, many bitmaps of this nature are included
in Microsoft Plus! for Windows 95 as well as with different third-party
software programs. In some cases changing the Picture property is all it
takes to replicate the problem. The bitmap will not display correctly on
the form. If the bitmap displays correctly initially, running the
program and switching between different applications and the desktop
will demonstrate the problem.
|