diff options
author | Laszlo Agocs <laszlo.agocs@qt.io> | 2023-10-20 17:45:09 +0200 |
---|---|---|
committer | Laszlo Agocs <laszlo.agocs@qt.io> | 2023-11-06 18:31:54 +0200 |
commit | bd78047df34fda3a56b8db069fc97280831ac696 (patch) | |
tree | c941973904d55c85e6682708aee082656d8325e0 /src/network/access/qhttpprotocolhandler.cpp | |
parent | 105a8d90bc2a29c48b6136970652dcedd1f0848e (diff) |
QVulkanWindow: Add a way to control post-1.0 Vulkan features
So now instead of filling out a VkPhysicalDeviceFeatures and
sending it in via VkDeviceCreateInfo::pEnabledFeatures,
we rather create a VkPhysicalDeviceFeatures2, which contains
a VkPhysicalDeviceFeatures (for 1.0 stuff) and a pNext
chain, and chain it via pNext to the VkDeviceCreateInfo.
QVulkanWindow will not do anything with post-1.0 features
by default. (in this regard it deviates from the QRhi
Vulkan backend which already tackles 1.1, 1.2, and 1.3
features as well, but this is not going to change)
However, applications may want to enable some of those still.
To enable this, add a new callback. When set, the callback is
invoked and the alternative behavior described above is
activated.
Fixes: QTBUG-117966
Change-Id: I8560a6b23421f545ee760e714cbe2ec2f6078406
Reviewed-by: Andy Nichols <andy.nichols@qt.io>
Diffstat (limited to 'src/network/access/qhttpprotocolhandler.cpp')
0 files changed, 0 insertions, 0 deletions