PHONE_BUTTON (TAPI)

A version of this page is also available for

Windows Embedded CE 6.0 R3

4/8/2010

This message is sent to notify the application that button press monitoring is enabled if it has detected a button press on the local phone.

Syntax

PHONE_BUTTON
    hPhone = (HPHONE) hPhoneDevice;
    dwCallbackInstance = (DWORD) hCallback;
    dwParam1 = (DWORD) idButtonOrLamp;
    dwParam2 = (DWORD) ButtonMode;
    dwParam3 = (DWORD) ButtonState;

Parameters

• hPhone
  Handle to the phone device.

• dwCallbackInstance
  Application's callback instance provided when opening the phone device.

• dwParam1
  Button/lamp identifier of the button that was pressed. Note that button identifiers zero through 11 always match the KEYPAD buttons, with '0' being button identifier zero, '1' being button identifier 1, and continued in this manner through button identifier 9, and with '*' being button identifier 10, and '#' being button identifier 11. You can obtain additional information about a button identifier by calling the phoneGetDevCaps function.

• dwParam2
  Button mode of the button. This parameter uses one of the PHONEBUTTONMODE constants.

• dwParam3
  Specifies whether this is a button-down event or a button-up event. This parameter uses one of the PHONEBUTTONSTATE.

Return Value

None.

Remarks

A PHONE_BUTTON message is sent whenever a button changes state. An application is guaranteed that for each button down event, it is eventually sent a corresponding button up event. A service provider that is incapable of detecting the actual button up is required to generate the button up message shortly after the button down message for each button press.

Requirements

See Also

Reference

phoneGetDevCaps