PFND3D10DDI_CREATEBLENDSTATE callback function (d3d10umddi.h)

Article
04/01/2021

The CreateBlendState function creates a blend state.

Syntax

PFND3D10DDI_CREATEBLENDSTATE Pfnd3d10ddiCreateblendstate;

void Pfnd3d10ddiCreateblendstate(
  D3D10DDI_HDEVICE unnamedParam1,
  const D3D10_DDI_BLEND_DESC *unnamedParam2,
  D3D10DDI_HBLENDSTATE unnamedParam3,
  D3D10DDI_HRTBLENDSTATE unnamedParam4
)
{...}

Parameters

unnamedParam1

hDevice [in]

A handle to the display device (graphics context).

unnamedParam2

pBlendDesc [in]

A pointer to a D3D10_DDI_BLEND_DESC structure that describes the parameters that the user-mode display driver uses to create a blend state.

unnamedParam3

hBlendState [in]

A handle to the driver's private data for the blend state.

unnamedParam4

hRTBlendState [in]

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

Return value

None

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 DestroyBlendState function to destroy the handle that the hBlendState parameter specifies.

The user-mode display driver is not required to create more than 4,096 unique instances of blend-state objects on a device at one time.

Requirements

Requirement	Value
Minimum supported client	Available in Windows Vista and later versions of the Windows operating systems.
Target Platform	Desktop
Header	d3d10umddi.h (include D3d10umddi.h)