D3DDDICB_ESCAPE - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3dumddi.h
typedef struct _D3DDDICB_ESCAPE {
[in] HANDLE hDevice;
[in] D3DDDI_ESCAPEFLAGS Flags;
[in/out] VOID *pPrivateDriverData;
[in] UINT PrivateDriverDataSize;
[in] HANDLE hContext;
} D3DDDICB_ESCAPE;
View the official Windows Driver Kit DDI referenceNo description available.
The D3DDDICB_ESCAPE structure describes information that a user-mode display driver shares with a display miniport driver.
hDevice [in]A handle to the display device (graphics context) that was originally passed to the user-mode display driver's CreateDevice or CreateDevice(D3D10) function or NULL, if the shared information is not associated with a display device.
Flags [in]A D3DDDI_ESCAPEFLAGS structure that indicates, in bit-field flags, how to share information. The user-mode display driver should specify the HardwareAccess bit-field flag to indicate that the display miniport driver must access graphics hardware in such a way that the operating system must perform the second level of synchronization into the display miniport driver for the DxgkDdiEscape call.
pPrivateDriverData [in/out]A pointer to a buffer that is allocated by the user-mode display driver that contains information that the user-mode display driver sends to the display miniport driver or that the user-mode display driver receives from the display miniport driver.
PrivateDriverDataSize [in]The size, in bytes, of the buffer that pPrivateDriverData points to.
hContext [in]A handle to the context that the pfnCreateContextCb function returned or NULL, if the shared information is not associated with a context. If the user-mode display driver sets hContext to a non-NULL value, the driver must have also set hDevice to a non-NULL value, and hDevice must correspond to the device that owns the context.