EVT_IDD_CX_MONITOR_GET_PHYSICAL_SIZE callback function (iddcx.h)

Article
02/22/2024

The OS calls EVT_IDD_CX_MONITOR_GET_PHYSICAL_SIZE to query the physical size of a remote EDID-less monitor.

Syntax

EVT_IDD_CX_MONITOR_GET_PHYSICAL_SIZE EvtIddCxMonitorGetPhysicalSize;

NTSTATUS EvtIddCxMonitorGetPhysicalSize(
  [in]  IDDCX_MONITOR MonitorObject,
  [out] IDARG_OUT_MONITORGETPHYSICALSIZE *pOutArgs
)
{...}

Parameters

[in] MonitorObject

The context for the monitor this OPM context should be created on.

[out] pOutArgs

Pointer to a IDARG_OUT_MONITORGETPHYSICALSIZE structure that contains information about the monitor size.

Return value

If the driver knows the physical size of the monitor, it should fill in the pOutArgs and return STATUS_SUCCESS. In the event the driver does not know the physical size, it should return STATUS_NO_DATA_DETECTED.

Remarks

This callback is only called for remote drivers that do not provide a monitor description for the specified monitor. If a remote driver does specify a monitor description for a given monitor, then the physical width and height will be taken from the description and this callback will not be called for that monitor.

To declare a remote ID driver:

An ID driver declares that it wants to create a remote ID adapter by setting the IDDCX_ADAPTER_FLAGS_REMOTE_SESSION_DRIVER bit in the IDDCX_ADAPTER_CAPS.Flags field when calling the IddCxAdapterInitAsync function. The OS tracks if the ID driver is being loaded due to the remote desktop stack connecting a remote session and will fail the IddCxAdapterInitAsync() call in the following two cases:

If an ID driver does not set the IDDCX_ADAPTER_FLAGS_REMOTE_SESSION_DRIVER flags for a device that was created by the OS remote desktop stack for a remote session
If an ID driver sets the IDDCX_ADAPTER_FLAGS_REMOTE_SESSION_DRIVER flags for a device that was not created by the OS remote desktop stack

Requirements

Requirement	Value
Minimum supported client	Windows 10, version 1903
Header	iddcx.h