BUG: FontChanged Event Fires Twice When a Property of a Font Object is Changed (208654)
The information in this article applies to:
- Microsoft Visual Basic Professional Edition for Windows 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q208654 SYMPTOMS
The FontChanged event sink fires more than once if the user sets a Stdfont object to a font more than once. Setting the font object twice may be necessary if the font object is destroyed for some reason, and then recreated. The expected behavior is that the FontChanged event fires only once when a property is changed.
RESOLUTION
Create the font object explicitly again after destroying it, and then set up the properties again. This makes the event fire only once.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 10/15/2002 |
---|
Keywords: | kbBug kbDSupport kbFont KB208654 |
---|
|