Article ID: 231465 - Last Review: January 16, 2004 - Revision: 3.0 BUG: No WM_MOUSEWHEEL Message is Received after Adding a UserControl to a FormThis article was previously published under Q231465 On This PageSYMPTOMS
After adding a User control to a Form, the Visual Basic design environment (IDE) ignores the WM_MOUSEWHEEL message when you roll the wheel of the mouse. This problem does not occur on Windows NT or Windows 2000.
CAUSE
The Visual Basic Design Environment (IDE) is not compatible with early versions of the Microsoft Intellimouse driver.
RESOLUTIONTo resolve this bug,
install version 4.11 or version 4.2 of the IntelliPoint driver. STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. MORE INFORMATIONSteps to Reproduce BehaviorWARNING: Failure to unhook a window before its imminent destruction may result in application errors, Invalid Page Faults, and data loss. This is due the fact that the new WindowProc function being pointed to no longer exists, but the window has not been notified of the change. Always unhook the sub-classed window upon unloading the sub-classed form or exiting the application. This is especially important while debugging an application that uses this technique within the Microsoft Visual Basic Development Environment (IDE). Pressing the End button or selecting End from the Run menu without unhooking may cause an Invalid Page Fault and close Microsoft Visual Basic. Changes to the active project will be lost.
REFERENCES
For additional information, please click the article number below
to view the article in the Microsoft Knowledge Base:
168795
(http://support.microsoft.com/kb/168795/EN-US/
)
HOWTO: Hook Into a Window's Messages using AddressOf
APPLIES TO
| Article Translations
|
Back to the top
