| Platform SDK: Broadcast Architecture |
The BPCSuspended object indicates whether the Video Access server has released all video devices. BPCSuspended has no methods, properties, or events. If you are developing applications in C++, you can use a header file that simplifies the process of suspending the server. For more information, see Suspending the Video Access Server Using Bpcsusp.h.
BPCSuspended is returned by the BPCSuspend.DeviceRelease method. If DeviceRelease is successful and the Video Access server releases all video devices, DeviceRelease returns a reference to a valid instance of BPCSuspended. The Video Access server remains suspended as long as this object exists.
To cause the Video Access server to resume work, release the BPCSuspended object by setting it to Nothing. The destruction of the BPCSuspended object notifies the Video Access server that it can once again connect to devices. Otherwise, the Video Access server is re-enabled when the object variable for BPCSuspended goes out of scope or the application that requested the suspension closes.
Your application should not use the BPCSuspend or BPCSuspended class while it is in a state in which cross-process COM calls are disallowed. For example, if your application is currently processing a call to the Win32 SendMessage function or a broadcast system message any cross-process COM calls fail with an RPC_E_CANTCALLOUT_ININPUTSYNCCALL error code. If your application is in such a state when it attempts to suspend the Video Access server, the running object table can become corrupt and lock up the server.
For more information on this process, see Suspending the Video Access Server.
Windows NT/2000: Unsupported.
Windows 95/98: Requires Windows 98.
Header: Declared in vidsvr.odl.
Import Library: Included as a resource in vid.ocx.