ActiveX Controls: Adding Stock Events to an ActiveX Control
| Overview | How Do I | FAQ | | Sample
Stock events differ from custom events in that they are automatically fired by class . COleControl contains predefined member functions that fire events resulting from common actions. Some common actions implemented by COleControl include single- and double-clicks on the control, keyboard events, and changes in the state of the mouse buttons. Event map entries for stock events are always preceded by the EVENT_STOCK prefix.
Stock Events Supported by ClassWizard
The COleControl class provides nine stock events, listed in the following table. You can specify the events you want in your control in the ActiveX Events tab in ClassWizard.
Stock Events
| Event | Firing function | Comments |
| Click | void FireClick( ) | Fired when the control captures the mouse, any BUTTONUP (left, middle, or right) message is received, and the button is released over the control. The stock MouseDown and MouseUp events occur before this event.
Event map entry: EVENT_STOCK_CLICK( ) |
| DblClick | void FireDblClick( ) | Similar to Click but fired when a BUTTONDBLCLK message is received.
Event map entry: EVENT_STOCK_DBLCLICK( ) |
| Error | void FireError( SCODE scode, LPCSTR lpszDescription, UINT nHelpID = 0 ) | Fired when an error occurs within your ActiveX control outside of the scope of a method call or property access.
Event map entry: EVENT_STOCK_ERROREVENT( ) |
| KeyDown | void FireKeyDown( short nChar, short nShiftState ) | Fired when a WM_SYSKEYDOWN or WM_KEYDOWN message is received.
Event map entry: EVENT_STOCK_KEYDOWN( ) |
| KeyPress | void FireKeyPress( short* pnChar ) | Fired when a WM_CHAR message is received.
Event map entry: EVENT_STOCK_KEYPRESS( ) |
| KeyUp | void FireKeyUp( short nChar, short nShiftState ) | Fired when a WM_SYSKEYUP or WM_KEYUP message is received.
Event map entry: EVENT_STOCK_KEYUP( ) |
| MouseDown | void FireMouseDown( short nButton, short nShiftState, float x, float y ) | Fired if any BUTTONDOWN (left, middle, or right) is received. The mouse is captured immediately before this event is fired.
Event map entry: EVENT_STOCK_MOUSEDOWN( ) |
| MouseMove | void FireMouseMove( short nButton, short nShiftState, float x, float y ) | Fired when a WM_MOUSEMOVE message is received.
Event map entry: EVENT_STOCK_MOUSEMOVE( ) |
| MouseUp | void FireMouseUp( short nButton, short nShiftState, float x, float y ) | Fired if any BUTTONUP (left, middle, or right) is received. The mouse capture is released before this event is fired.
Event map entry: EVENT_STOCK_MOUSEUP( ) |
| ReadyStateChange | void FireReadyStateChange( ) | Fired when a control transitions to the next ready state due to the amount of data received.
Event map entry: EVENT_STOCK_READYSTATECHANGE( ) |
Adding a Stock Event Using ClassWizard
Adding stock events requires less work than adding custom events because the firing of the actual event is handled automatically by the base class, COleControl. The following procedure adds a stock event to a control that was developed using ControlWizard. The event, called KeyPress, fires when a key is pressed and the control is active. This procedure can also be used to add other stock events. Simply substitute the desired stock event name for KeyPress.
To add the KeyPress stock event using ClassWizard
Load your control’s project.
On the View menu, click ClassWizard.
Click the ActiveX Events tab.
Select the name of your control class from the Class Name box.
Click Add Event.
In the External Name box, click KeyPress.
Click OK.
Click OK again to confirm your choices and exit ClassWizard.
ClassWizard Changes for Stock Events
Because stock events are handled by the control’s base class, ClassWizard does not change your class declaration in any way. It simply adds the event to the control’s event map and makes an entry in its .ODL file. The following line is added to the control’s event map, located in the control class implementation (.CPP) file:
EVENT_STOCK_KEYPRESS()
Adding this code fires a KeyPress event when a WM_CHAR message is received and the control is active. The KeyPress event can be fired at other times by calling its firing function (for example, FireKeyPress) from within the control code.
ClassWizard adds the following line of code to the control’s .ODL file:
[id(DISPID_KEYPRESS)] void KeyPress(short* KeyAscii);
This line associates the KeyPress event with its standard dispatch ID and allows the container to anticipate the KeyPress event.
See Also ActiveX Controls: Methods,