From 0d80dab2c09cb0bbeeaa075fa79b6c1356d1d37a Mon Sep 17 00:00:00 2001 From: Adam Sawicki Date: Wed, 1 Aug 2018 16:20:24 +0200 Subject: [PATCH] Fixed minor documentation mistakes - issue #32 - thanks @dgough ! --- src/vk_mem_alloc.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/vk_mem_alloc.h b/src/vk_mem_alloc.h index 03a0e27..149445e 100644 --- a/src/vk_mem_alloc.h +++ b/src/vk_mem_alloc.h @@ -298,7 +298,7 @@ The library provides following functions for mapping of a specific #VmaAllocatio They are safer and more convenient to use than standard Vulkan functions. You can map an allocation multiple times simultaneously - mapping is reference-counted internally. You can also map different allocations simultaneously regardless of whether they use the same `VkDeviceMemory` block. -They way it's implemented is that the library always maps entire memory block, not just region of the allocation. +The way it's implemented is that the library always maps entire memory block, not just region of the allocation. For further details, see description of vmaMapMemory() function. Example: @@ -312,7 +312,7 @@ struct ConstantBuffer ConstantBuffer constantBufferData; VmaAllocator allocator; -VmaBuffer constantBuffer; +VkBuffer constantBuffer; VmaAllocation constantBufferAllocation; // You can map and fill your buffer using following code: