Vulkan-Docs/doc/specs/vulkan/appendices/VK_EXT_direct_mode_display.txt
Petr Kraus f388b5aece Cute up extension typography
- make extension names links where appropriate
- use tick markup
elsewhere
2017-12-20 18:00:32 +01:00

60 lines
1.6 KiB
Plaintext

include::meta/VK_EXT_direct_mode_display.txt[]
*Last Modified Date*::
2016-12-13
*IP Status*::
No known IP claims.
*Contributors*::
- Pierre Boudier, NVIDIA
- James Jones, NVIDIA
- Damien Leone, NVIDIA
- Pierre-Loup Griffais, Valve
- Liam Middlebrook, NVIDIA
This is extension, along with related platform exentions, allows
applications to take exclusive control of displays associated with a native
windowing system.
This is especially useful for virtual reality applications that wish to hide
HMDs (head mounted displays) from the native platform's display management
system, desktop, and/or other applications.
=== New Enum Constants
None.
=== New Enums
None.
=== New Structures
None.
=== New Functions
* flink:vkReleaseDisplayEXT
=== Issues
1) Should this extension and its related platform-specific extensions
leverage <<VK_KHR_display>>, or provide separate equivalent interfaces.
*RESOLVED*: Use <<VK_KHR_display>> concepts and objects.
<<VK_KHR_display>> can be used to enumerate all displays on the system,
including those attached to/in use by a window system or native platform,
but <<VK_KHR_display_swapchain>> will fail to create a swapchain on in-use
displays.
This extension and its platform-specific children will allow applications to
grab in-use displays away from window systems and/or native platforms,
allowing them to be used with <<VK_KHR_display_swapchain>>.
2) Are separate calls needed to acquire displays and enable direct mode?
*RESOLVED*: No, these operations happen in one combined command.
Acquiring a display puts it into direct mode.
=== Version History
* Revision 1, 2016-12-13 (James Jones)
- Initial draft