PFND3D10DDI_DESTROYBLENDSTATE - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// d3d10umddi.h
PFND3D10DDI_DESTROYBLENDSTATE Pfnd3d10ddiDestroyblendstate;
VOID Pfnd3d10ddiDestroyblendstate(
D3D10DDI_HDEVICE unnamedParam1,
D3D10DDI_HBLENDSTATE unnamedParam2
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The DestroyBlendState function destroys the specified blend state object. The blend state object can be destroyed only if it is not currently bound to a display device.
unnamedParam1hDevice [in]
A handle to the display device (graphics context).
unnamedParam2hBlendState [in]
A handle to the driver's private data for the blend state object to destroy. The Microsoft Direct3D runtime will free the memory region that it previously allocated for the object. Therefore, the driver can no longer access this memory region.
The driver can use the pfnSetErrorCb callback function to set an error code.
The driver should not encounter any error, except for D3DDDIERR_DEVICEREMOVED. Therefore, if the driver passes any error, except for D3DDDIERR_DEVICEREMOVED, in a call to the pfnSetErrorCb function, the Direct3D runtime will determine that the error is critical. Even if the device was removed, the driver is not required to return D3DDDIERR_DEVICEREMOVED; however, if device removal interfered with the operation of DestroyBlendState (which typically should not happen), the driver can return D3DDDIERR_DEVICEREMOVED.