Skip to content

Commit

Permalink
add link to CategoryRender
Browse files Browse the repository at this point in the history
  • Loading branch information
thatcosmonaut committed Oct 4, 2024
1 parent ba60a27 commit 1ce350c
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions include/SDL3/SDL_gpu.h
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@
*
* If the app needs to read back data from texture or buffers, the API
* has an efficient way of doing this, provided that the app is willing to tolerate some latency.
* When the app uses SDL_DownloadFromGPUTexture or SDL_DownloadFromGPUBuffer, submitting the command buffer with
* When the app uses SDL_DownloadFromGPUTexture() or SDL_DownloadFromGPUBuffer(), submitting the command buffer with
* SubmitGPUCommandBufferAndAcquireFence() will return a fence handle that the app
* can poll or wait on in a thread. Once the fence indicates that the command buffer is done processing,
* it is safe to read the downloaded data. Make sure to call SDL_ReleaseGPUFence() when done with the fence.
Expand All @@ -110,7 +110,7 @@
* This is an extremely quick overview that leaves out several important
* details. Already, though, one can see that GPU programming can be quite
* complex! If you just need simple 2D graphics, the
* [Render API](CategoryRender) is much easier to use but still
* [Render API](https://wiki.libsdl.org/SDL3/CategoryRender) is much easier to use but still
* hardware-accelerated. That said, even for 2D applications the performance benefits
* and expressiveness of the GPU API are significant.
*
Expand Down

0 comments on commit 1ce350c

Please sign in to comment.