OWLNext 7.0
Borland's Object Windows Library for the modern age
|
After you have derived your new class, you need to build a response table for it.
The response table for this class looks like a normal response table; you still need to handle all the regular command messages and events you normally do. The only addition is the EV_VBXEVENTNAME macro to handle the new class of messages from your VBX controls.
The EV_VBXEVENTNAME macro is defined as follows:
The three parameters are
Parameter | Description |
ID | The control ID. You can find this ID either as the second parameter to both constructors or as the resource ID in the resource file. |
Event | A string identifying the event name. This name is dependent on the control and can be one of the standard VBX event names or a custom event name. If the control is from a third-party VBX control library, you can find this event name by looking in the control reference guide. |
EvHandler | The handler function for this event and control. The EvHandler function has the following signature: |
When a message is received from a VBX control by its parent, the parent dispatches the message to the handler function that corresponds to the correct control and event. When it calls the function, the parent passes it a pointer to a VBXEVENT structure.