Providing Mouse Interaction While Inactive

|  Overview |  How Do I |  FAQ |  |  Sample

If your control is not immediately activated, you may still want it to process WM_SETCURSOR and WM_MOUSEMOVE messages, even though the control has no window of its own. This can be accomplished by enabling COleControl’s implementation of the IPointerInactive interface, which is disabled by default. (See the ActiveX SDK for a description of this interface.) To enable it, include the pointerInactive flag in the set of flags returned by :

DWORD CMyCtrl::GetControlFlags()
{
    return COleControl::GetControlFlags() | pointerInactive;
}

The code to include this flag is automatically generated if you select the Mouse Pointer Notifications When Inactive option on the Advanced ActiveX Features page when creating your control with ControlWizard.

When the IPointerInactive interface is enabled, the container delegates WM_SETCURSOR and WM_MOUSEMOVE messages to it. COleControl’s implementation of IPointerInactive dispatches the messages through your control’s message map after adjusting the mouse coordinates appropriately. You can process the messages just like ordinary window messages by adding the corresponding entries to the message map. In your handlers for these messages, avoid using the m_hWnd member variable (or any member function that uses it) without first checking that its value is not NULL.

You may also want an inactive control to be the target of an OLE drag-and-drop operation. This requires activating the control at the moment the user drags an object over it, so that the control’s window can be registered as a drop target. To cause activation to occur during a drag, override , and return the POINTERINACTIVE_ACTIVATEONDRAG flag:

DWORD CMyCtrl::GetActivationPolicy()
{
    return POINTERINACTIVE_ACTIVATEONDRAG;
}

Enabling the IPointerInactive interface typically means that you want the control to be capable of processing mouse messages at all times. To get this behavior in a container that doesn’t support the IPointerInactive interface, you need to have your control always activated when visible, which means the control should include the OLEMISC_ACTIVATEWHENVISIBLE flag among its miscellaneous flags. However, to prevent this flag from taking effect in a container that does support IPointerInactive, you can also specify the OLEMISC_IGNOREACTIVATEWHENVISIBLE flag:

static const DWORD BASED_CODE _dwMyOleMisc =
    OLEMISC_ACTIVATEWHENVISIBLE |
    OLEMISC_IGNOREACTIVATEWHENVISIBLE |
    OLEMISC_SETCLIENTSITEFIRST |
    OLEMISC_INSIDEOUT |
    OLEMISC_CANTLINKINSIDE |
    OLEMISC_RECOMPOSEONRESIZE;