| UID | title | description | old-location | tech.root | ms.date | keywords | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | f1_keywords | topic_type | api_type | api_location | api_name | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NF:video.VideoPortCreateEvent |
VideoPortCreateEvent function (video.h) |
The VideoPortCreateEvent function creates an event object. |
display\videoportcreateevent.htm |
display |
05/10/2018 |
|
VideoPortCreateEvent, VideoPortCreateEvent function [Display Devices], VideoPort_Functions_29412925-5117-4759-b4ea-b4adb4358a8c.xml, display.videoportcreateevent, video/VideoPortCreateEvent |
video.h |
Video.h |
Desktop |
Available in Windows XP and later versions of the Windows operating systems. |
Videoprt.lib |
Videoprt.sys |
PASSIVE_LEVEL |
Windows |
|
|
|
|
|
The VideoPortCreateEvent function creates an event object.
Pointer to the miniport driver's device extension.
Specifies the event type and initial event state. This can be an ORed combination of the following flags:
| Flag | Meaning |
|---|---|
| INITIAL_EVENT_SIGNALED | Set this flag to indicate the signaled state for the event object. Otherwise, the initial state of the event is nonsignaled. |
| NOTIFICATION_EVENT | Set this flag to create a notification event. If this flag is not set, a synchronization event is created. |
Is currently ignored by the video port driver and must be set to NULL.
Pointer to the memory location at which a pointer to the event object will be returned.
VideoPortCreateEvent returns NO_ERROR if the event object is successfully created.
When a synchronization event is set to the signaled state, a single thread that was waiting for the signaled state is released (its dispatch state transitions from waiting to ready, standby, or running), and the event is automatically reset to the nonsignaled state.
When a notification event is set to the signaled state, all threads that were waiting for the signaled state are released, and the event remains in the signaled state until it is explicitly reset to the nonsignaled state.