PFND3D10DDI_CREATEELEMENTLAYOUT - NtDoc

Native API online documentation, based on the System Informer (formerly Process Hacker) phnt headers
// d3d10umddi.h

PFND3D10DDI_CREATEELEMENTLAYOUT Pfnd3d10ddiCreateelementlayout;

VOID Pfnd3d10ddiCreateelementlayout(
  D3D10DDI_HDEVICE unnamedParam1,
  const D3D10DDIARG_CREATEELEMENTLAYOUT *unnamedParam2,
  D3D10DDI_HELEMENTLAYOUT unnamedParam3,
  D3D10DDI_HRTELEMENTLAYOUT unnamedParam4
)
{...}
View the official Windows Driver Kit DDI reference

NtDoc

No description available.

Windows Driver Kit DDI reference (nc-d3d10umddi-pfnd3d10ddi_createelementlayout)

PFND3D10DDI_CREATEELEMENTLAYOUT callback function

Description

The CreateElementLayout function creates an element layout.

Parameters

unnamedParam1

hDevice [in]

A handle to the display device (graphics context).

unnamedParam2

pCreateElementLayout [in]

A pointer to a D3D10DDIARG_CREATEELEMENTLAYOUT structure that describes the parameters that the user-mode display driver uses to create an element layout.

unnamedParam3

hElementLayout [in]

A handle to the driver's private data for the element layout.

unnamedParam4

hRTElementLayout [in]

A handle to the element layout that the driver should use anytime it calls back into the Direct3D runtime.

Remarks

The driver can use the pfnSetErrorCb callback function to set an error code.

The driver can pass E_OUTOFMEMORY (if the driver runs out of memory) or D3DDDIERR_DEVICEREMOVED (if the device has been removed) in a call to the pfnSetErrorCb function. The Direct3D runtime will determine that any other errors are critical. If the driver passes any errors, including D3DDDIERR_DEVICEREMOVED, the Direct3D runtime will determine that the handle is invalid; therefore, the runtime will not call the DestroyElementLayout function to destroy the handle that the hElementLayout parameter specifies.

See also

CalcPrivateElementLayoutSize

D3D10DDIARG_CREATEELEMENTLAYOUT

D3D10DDI_DEVICEFUNCS

DestroyElementLayout

pfnSetErrorCb