BUG: SSCommand Click Fired with Double-Click in Common DialogLast reviewed: October 3, 1996Article ID: Q149277 |
The information in this article applies to:
SYMPTOMSDouble-clicking a file name in a common dialog box that happens to be displayed immediately above an SSCommand button will cause the Click event for the SSCommand button to be fired.
WORKAROUNDThis problem can be worked around in two ways. The easiest and quickest route is to replace all SSCommand buttons with regular command buttons. The regular command button does not show this behavior. Another alternative is to set the enabled property of the SSCommand button to false immediately before showing the common dialog box. If this route is taken then a timer must be utilized to switch the enabled property of the SSCommand back to True. If Enabled is set to true immediately after the common dialog box returns (or even after a delay loop), the SSCommand will still have its click event fired. The following is a step-by-step example for this fix (this can be followed after the reproduction sample below):
STATUSMicrosoft has confirmed this to be an issue in the Microsoft products listed at the beginning of this article. Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
Steps to Reproduce
|
Additional reference words: 4.00 vb4win vb4all
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |