1394API.DLL API如何使用 |
尚未結案
|
kkccgg
初階會員 發表:50 回覆:54 積分:30 註冊:2002-07-28 發送簡訊給我 |
|
chris_shieh
高階會員 發表:46 回覆:308 積分:240 註冊:2004-04-26 發送簡訊給我 |
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/appendix/hh/appendix/1394_api_cdfdb899-e979-4b58-b442-8abf62d95817.xml.asp Windows Applications
Windows based clients using 1394API.DLL are required to register during initialization using the RegisterClient API. When the client terminates, it must call the DeRegisterClient API. After a client registers its hWnd, it can expect to receive messages when an IEEE 1394 bus reset or a IEEE 1394 device change occurs. It will receive either a NOTIFY_DEVICE_CHANGE message when an IEEE 1394 device is added/removed, or a NOTIFY_BUS_RESET when a IEEE 1394 bus reset occurs. NOTIFY_DEVICE_CHANGE
The client will receive this message whenever an IEEE 1394 device has been added or removed. When the client receives this notification, it is required to call the GetDeviceList API to get an updated list of devices available. NOTIFY_BUS_RESET
The client will receive this message whenever an IEEE 1394 bus reset occurs. Console Applications
The use of the RegisterClient and DeRegisterClient API's is meant for the application to receive notification of bus resets and device changes. It is not possible for a console application to receive these notifications. Instead, the console application will call the GetDeviceList API in order to get a list of devices available. No other action is required by a console application. The 1394API.DLL API
|
本站聲明 |
1. 本論壇為無營利行為之開放平台,所有文章都是由網友自行張貼,如牽涉到法律糾紛一切與本站無關。 2. 假如網友發表之內容涉及侵權,而損及您的利益,請立即通知版主刪除。 3. 請勿批評中華民國元首及政府或批評各政黨,是藍是綠本站無權干涉,但這裡不是政治性論壇! |