projects / platform / upstream / Vulkan-Tools.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 66d9c4c) | patch
cube: Handle occlusion where currentExtent == 0xFFFFFFFF
authorJoshua Ashton <joshua@froggi.es>
Thu, 17 Jun 2021 17:30:14 +0000 (18:30 +0100)
committerjeremyk-lunarg <jeremyk@lunarg.com>
Thu, 17 Jun 2021 19:12:11 +0000 (13:12 -0600)
commita680671d95bf7b3846cb20f1cbfc1c405db0511b
tree2f64206c0232ee10036deb95e2e9db5ea931d34btree | snapshot
parent66d9c4c09b44ac0e05fd86925f43404109521943commit | diff
cube: Handle occlusion where currentExtent == 0xFFFFFFFF

The Vulkan spec states that: "On some platforms, it is normal that maxImageExtent may become (0, 0), for example when the window is minimized. In such a case, it is not possible to create a swapchain due to the Valid Usage requirements."

Yet vkcube previously only handled this path for platforms where currentExtent != 0xFFFFFFFF.
cube/cube.c diff | blob | history
Domain: Graphics System / GL;