KhronosGroup / KhronosGroup/Vulkan-Docs
`minScaledImageExtent` should not have `0xFFFFFFFF` special value?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
I don't immediately folow the logic of VkSurfacePresentScalingCapabilitiesEXT::minScaledImageExtent having the (0xFFFFFFFF, 0xFFFFFFFF) special value. It looks like a copy-paste error from currentExtent spec. It feels a reasonable min value would still be needed for swapchain creation, even if the window size is determined by the first present op.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the specification definition of VkSurfacePresentScalingCapabilitiesEXT::minScaledImageExtent and compare its (0xFFFFFFFF, 0xFFFFFFFF) special value with currentExtent. Determine whether the value is intentional or a copy-paste error, then document or correct the specification so the required minimum extent and swapchain-creation behavior are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100