Microsoft KB Archive/215394

= BUG: Courier and Symbol Fonts Might Not Appear on HPC =

Q215394

-

The information in this article applies to:


 * Microsoft Windows CE Toolkit for Visual Basic 6.0, version 1.0

-

SYMPTOMS
When you create a Windows CE Toolkit for Visual Basic (VBCE) application targeting a Handheld PC class device (running Windows CE 2.0) and try to change the font to either Courier or Symbol, the font is mapped to the Arial font. The expected behavior is that the font should change to the new value of the FontName property. This problem does not occur when targeting the emulator or when targeting devices running Windows CE 2.11 or later.

STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

MORE INFORMATION
This section shows you how to create a sample project that demonstrates the bug behavior.

Steps to Reproduce Behavior

 * 1) Start a new Windows CE HPC project in Visual Basic. Form1 is created by default.
 * 2) Add three CommandButtons and a TextBox to Form1.
 * 3) Copy the following code to the code window of Form1.
 * 4) Run the project (targeting the emulator) and click Command1. Notice that the font changes to Times New Roman.
 * 5) Click Command2 and Command3 and note that the font changes accordingly.
 * 6) Exit the application.
 * 7) Run the project again, this time targeting the remote device, and click Command1. Note that the font changes to Times New Roman.
 * 8) Click Command2 and Command3. Note that the font becomes Arial. The expected behavior is that the fonts should change as they did when the project was run in emulation mode.

Additional query words: wce vbce vbce6

Keywords : kbToolkit kbVBp600bug kbOSWinCEsearch kbGrpDSVB

Issue type : kbbug

Technology : kbVBSearch kbAudDeveloper kbWinCETKVBSearch kbWinCESearch kbWinCETK100VB600

Last Reviewed: October 2, 1999

-

[mailto:MSDN@MICROSOFT.COM Send feedback to Microsoft]

© 2002 Microsoft Corporation. All rights reserved.