1include::meta/VK_EXT_acquire_xlib_display.txt[] 2 3*Last Modified Date*:: 4 2016-12-13 5*IP Status*:: 6 No known IP claims. 7*Contributors*:: 8 - Dave Airlie, Red Hat 9 - Pierre Boudier, NVIDIA 10 - James Jones, NVIDIA 11 - Damien Leone, NVIDIA 12 - Pierre-Loup Griffais, Valve 13 - Liam Middlebrook, NVIDIA 14 - Daniel Vetter, Intel 15 16This extension allows an application to take exclusive control on a display 17currently associated with an X11 screen. 18When control is acquired, the display will be deassociated from the X11 19screen until control is released or the specified display connection is 20closed. 21Essentially, the X11 screen will behave as if the monitor has been unplugged 22until control is released. 23 24=== New Enum Constants 25 26None. 27 28=== New Enums 29 30None. 31 32=== New Structures 33 34None. 35 36=== New Functions 37 38 * flink:vkAcquireXlibDisplayEXT 39 * flink:vkGetRandROutputDisplayEXT 40 41=== Issues 42 431) Should flink:vkAcquireXlibDisplayEXT take an RandR display ID, or a 44Vulkan display handle as input? 45 46*RESOLVED*: A Vulkan display handle. 47Otherwise there would be no way to specify handles to displays that had been 48"`blacklisted`" or prevented from being included in the X11 display list by 49some native platform or vendor-specific mechanism. 50 512) How does an application figure out which RandR display corresponds to a 52Vulkan display? 53 54*RESOLVED*: A new function, flink:vkGetRandROutputDisplayEXT, is introduced 55for this purpose. 56 573) Should flink:vkGetRandROutputDisplayEXT be part of this extension, or a 58general Vulkan + RandR or Vulkan + Xlib extension? 59 60*RESOLVED*: To avoid yet another extension, include it in this extension. 61 62=== Version History 63 64 * Revision 1, 2016-12-13 (James Jones) 65 - Initial draft 66