KB186472 - PRB: MFC Subclassed Static Control Does Not Work in VB5

RESOLUTION

Open the Control Workspace (.dsw) file in Developer Studio.

Use the Class wizard to add a message handler for WM_NCHITTEST. Edit the code to return HTCLIENT. Change your code to look like the following:

      UINT CMySubClCtrl::OnNcHitTest(CPoint point)
      {
        // TODO: Add your message handler code here and/or call default.

        //Return COleControl::OnNcHitTest(point);
        return HTCLIENT;
      }

Rebuild the control.

MORE INFORMATION

Steps to Reproduce Behavior

Create an ActiveX Control with the MFC ActiveX Control Wizard. Select the STATIC Window class to subclass.

Use the Class wizard to add a message handler for WM_LBUTTONDOWN. Change your code to look like the following:

      void CMySubClCtrl::OnLButtonDown(UINT nFlags, CPoint point)
      {
        AfxMessageBox("StaticSubclass");
        COleControl::OnLButtonDown(nFlags, point);
      }

Build this control.
Launch Visual Basic and create a new Standard EXE project.
Click Components on the Project menu and select the ActiveX Control you just created.
Place the ActiveX control on Form1.
Run the project.
Click the ActiveX control. Notice that no MessageBox appears and that if you double-click the control, the control's property page appears.

NOTE: In step 1, if the EDIT Window class is subclassed instead of the STATIC Window class, the MFC ActiveX control works as expected. The information in this article is specific to the STATIC Window class.

PRB: MFC Subclassed Static Control Does Not Work in VB5

SYMPTOMS

RESOLUTION

STATUS

MORE INFORMATION

Steps to Reproduce Behavior