Platform SDK: TAPI |
The TSPI PHONE_BUTTON message is sent to the PHONEEVENT callback function to notify TAPI that it has detected a button press on a phone device that TAPI has open and for which button press monitoring is enabled.
PHONE_BUTTON htPhone = (HTAPIPHONE) hPhoneDevice; dwMsg = (DWORD) PHONE_BUTTON; dwParam1 = (DWORD) idButtonLamp; dwParam2 = (DWORD) PhoneButtonMode; dwParam3 = (DWORD) PhoneButtonState;
The set of phone button events that is reported is selected by the TSPI_phoneSetStatusMessages function. The service provider must send PHONE_BUTTON messages for at least the set of button press events selected through that procedure. The service provider can send more than this set but should limit its messages to this set for performance reasons.
A PHONE_BUTTON message is sent whenever a button changes state. The service provider must guarantee that each button DOWN event is strictly paired with a button UP event, in that order. Note that a service provider that can detect only one of the button press or release events should expand the event it does detect into a button DOWN message followed by a button UP message.
Windows NT/2000: Requires Windows NT 4.0 SP3 or later.
Windows 95/98: Requires Windows 95 or later.
Version: Requires TAPI 2.0 or later.
Header: Declared in Tapi.h.
PHONEBUTTONFUNCTION_ Constants, PHONEBUTTONMODE_ Constants, PHONEBUTTONSTATE_ Constants, PHONEEVENT, PHONESTATUS, TSPI_phoneGetButtonInfo, TSPI_phoneGetDevCaps, TSPI_phoneSetStatusMessages,