Skip to content

Add full name for vkBindXMemory functions in french translation #259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 29, 2021
Merged

Add full name for vkBindXMemory functions in french translation #259

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion fr/06_Texture_mapping/00_Images.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -280,7 +280,7 @@ vkBindImageMemory(device, textureImage, textureImageMemory, 0);

L'allocation de la mémoire nécessaire à une image fonctionne également de la même façon que pour un buffer. Seuls les
noms de deux fonctions changent : `vkGetBufferMemoryRequirements` devient `vkGetImageMemoryRequirements` et
`vkBindBuffer` devient `vkBindImage`.
`vkBindBufferMemory` devient `vkBindImageMemory`.

Cette fonction est déjà assez grande ainsi, et comme nous aurons besoin d'autres images dans de futurs chapitres, il est
judicieux de déplacer la logique de leur création dans une fonction, comme nous l'avons fait pour les buffers. Voici
Expand Down