Important: |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This message is sent to inform the application of the creation of a new line device.
Syntax
LINE_CREATE dwDevice = (DWORD) 0; dwCallbackInstance = (DWORD) 0; dwParam1 = (DWORD) idDevice; dwParam2 = (DWORD) 0; dwParam3 = (DWORD) 0; |
Parameters
- dwDevice
-
Not used by this message. Value is NULL.
- dwCallbackInstance
-
Not used by this message. Value is NULL.
- dwParam1
-
Value that specifies the hDeviceIDof the newly created device.
- dwParam2
-
Not used by this message. Value is NULL.
- dwParam3
-
Not used by this message. Value is NULL.
Return Value
None.
Remarks
Older applications (that negotiated TAPI 1.3) are sent a LINE_LINEDEVSTATE (TAPI)message specifying LINEDEVSTATE_REINIT, which requires them to shut down their use of the API and call the lineInitializefunction again to obtain the new number of devices. Unlike previous versions of TAPI, however, this version does not require allapplications to shut down before allowing applications to reinitialize. Re-initialization can take place immediately when a new device is created. Complete shutdown is still required when a service provider is removed from the system.
Applications supporting TAPI 1.4 or later are sent a LINE_CREATE message. This informs them of the existence of the new device and its new device identifier. The application can then choose whether or not to attempt working with the new device at its leisure. This message is sent to all applications supporting this or subsequent versions of the API that have called lineInitialize, including those that do not have any line devices open at the time.
Requirements
Header | tapi.h |
Windows Embedded CE | Windows CE 1.0 and later |
Windows Mobile | Windows Mobile Version 5.0 and later |