Skip to content

Commit d26b5e1

Browse files
authored
Typo fix (#278)
* Typo fix Changed VkFormat to vk::Format in findDepthFormat * Typo fix k::ImageLayout::eUndefined to vk::ImageLayout::eUndefined
1 parent 426d981 commit d26b5e1

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

en/07_Depth_buffering.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -235,7 +235,7 @@ We'll use this function now to create a `findDepthFormat` helper function to sel
235235

236236
[,c++]
237237
----
238-
VkFormat findDepthFormat() {
238+
vk::Format findDepthFormat() {
239239
return findSupportedFormat(
240240
{vk::Format::eD32Sfloat, vk::Format::eD32SfloatS8Uint, vk::Format::eD24UnormS8Uint},
241241
vk::ImageTiling::eOptimal,
@@ -385,7 +385,7 @@ transition_image_layout(
385385
vk::ImageAspectFlagBits::eDepth);
386386
----
387387

388-
Unlike as with the color image we don't need multiple barriers here. As we don't care for the contents of the depth attachment once the frame is finished, we can always translate from `k::ImageLayout::eUndefined`. What's special about this layout, is the fact that you can always use it as a source without having to care what happens before.
388+
Unlike as with the color image we don't need multiple barriers here. As we don't care for the contents of the depth attachment once the frame is finished, we can always translate from `vk::ImageLayout::eUndefined`. What's special about this layout, is the fact that you can always use it as a source without having to care what happens before.
389389

390390
Also make sure you adjust all other calls to the `transition_image_layout` function call to pass the correct image aspect:
391391

0 commit comments

Comments
 (0)