Skip to content

SDL3/SDL_LockTexture: Updated. #819

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

SDL3/SDL_LockTexture: Updated. #819

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
11 changes: 11 additions & 0 deletions SDL3/SDL_LockTexture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,17 @@ application level.
You must use [SDL_UnlockTexture](SDL_UnlockTexture)() to unlock the pixels
and apply any changes.

*Note on SDL_LockTexture vs SDL_UpdateTexture:*
On the software renderer, you can write directly to the final destination
with SDL_LockTexture, whereas SDL_UpdateTexture will need to make a copy
from your buffer to SDL's.
On the other renderers, it's probably the same (the GLES2 renderer, for
example, literally just calls SDL_UpdateTexture for its SDL_UnlockTexture
implementation)... but if you ever need a software renderer, this is the
thing that would benefit most from texture locking.
But in real life, with actual GPUs, it doesn't really matter a whole lot.


## Thread Safety

This function should only be called on the main thread.
Expand Down