phoneGetStatusMessages (Compact 2013)
3/26/2014
This function returns which phone-state changes on the specified phone device generate a callback to the application.
Syntax
LONG WINAPI phoneGetStatusMessages(
HPHONE hPhone,
LPDWORD lpdwPhoneStates,
LPDWORD lpdwButtonModes,
LPDWORD lpdwButtonStates
);
Parameters
- hPhone
Handle to the open phone device to be monitored.
- lpdwPhoneStates
Pointer to a DWORD holding zero, one or more of the PHONESTATE constants. These flags specify the set of phone status changes and events for which the application can receive notification messages. Monitoring can be individually enabled and disabled for:
- lpdwButtonModes
Pointer to a DWORD containing flags that specify the set of phone-button modes for which the application can receive notification messages. This parameter uses zero, one or more of the PHONEBUTTONMODE constants.
- lpdwButtonStates
Pointer to a DWORD that contains flags specifying the set of phone button state changes for which the application can receive notification messages. This parameter uses zero, one or more of the PHONEBUTTONSTATE constants.
Return Value
Returns zero if the request succeeds or a negative error number if an error occurs. The following table shows the return values for this function.
Value |
Description |
---|---|
PHONEERR_INVALPHONEHANDLE |
The handle to the open phone device is invalid. |
PHONEERR_NOMEM |
Not enough memory is available. |
PHONEERR_INVALPOINTER |
A pointer is invalid. |
PHONEERR_RESOURCEUNAVAIL |
The resources are unavailable. |
PHONEERR_OPERATIONFAILED |
The operation failed. |
PHONEERR_UNINITIALIZED |
A parameter is uninitialized. |
Remarks
An application can use phoneGetStatusMessages to query the generation of the corresponding messages. Message generation can be controlled by phoneSetStatusMessages. All phone status messages are disabled by default.
Requirements
Header |
tapi.h |
Library |
TAPI32.dll |
See Also
Reference
TAPI Phone Device Functions
phoneGetDevCaps
phoneSetStatusMessages