VkDisplayPropertiesKHR

The VkDisplayPropertiesKHR structure is defined as:

typedef struct VkDisplayPropertiesKHR {
    VkDisplayKHR display;
    const char* displayName;
    VkExtent2D physicalDimensions;
    VkExtent2D physicalResolution;
    VkSurfaceTransformFlagsKHR supportedTransforms;
    VkBool32 planeReorderPossible;
    VkBool32 persistentContent;
} VkDisplayPropertiesKHR;

pub struct DisplayPropertiesKHR {
    display: vk::DisplayKHR, // Handle of the display object
    display_name: *const c_char, // Name of the display
    physical_dimensions: vk::Extent2D, // In millimeters?
    physical_resolution: vk::Extent2D, // Max resolution for CRT?
    supported_transforms: vk::SurfaceTransformFlagsKHR, // one or more bits from VkSurfaceTransformFlagsKHR
    plane_reorder_possible: vk::Bool32, // VK_TRUE if the overlay plane's z-order can be changed on this display.
    persistent_content: vk::Bool32, // VK_TRUE if this is a "smart" display that supports self-refresh/internal buffering.
}

• display is a handle that is used to refer to the display described here. This handle will be valid for the lifetime of the Vulkan instance.
• displayName is NULL or a pointer to a null-terminated UTF-8 string containing the name of the display. Generally, this will be the name provided by the display’s EDID. If NULL, no suitable name is available. If not NULL, the string pointed to must remain accessible and unmodified as long as display is valid.
• physicalDimensions describes the physical width and height of the visible portion of the display, in millimeters.
• physicalResolution describes the physical, native, or preferred resolution of the display.

• supportedTransforms is a bitmask of VkSurfaceTransformFlagBitsKHR describing which transforms are supported by this display.
• planeReorderPossible tells whether the planes on this display can have their z order changed. If this is VK_TRUE, the application can re-arrange the planes on this display in any order relative to each other.
• persistentContent tells whether the display supports self-refresh/internal buffering. If this is true, the application can submit persistent present operations on swapchains created against this display.