Mercurial > sdl-ios-xcode
view docs/man3/SDL_LockSurface.3 @ 720:f90d80d68071
N Sep 17 8791 Sam Lantinga Re: tks source released
Date: Sun, 07 Sep 2003 02:51:58 +0200
From: Stephane Marchesin
Subject: [SDL] Two little patches
Compiling SDL with a recent gcc (gcc 3.3.1, 3.3 doesn't have this
behaviour) gives some nasty warnings :
SDL_blit_A.c: In function `BlitRGBtoRGBSurfaceAlpha128MMX':
SDL_blit_A.c:223: warning: integer constant is too large for "long" type
SDL_blit_A.c:225: warning: integer constant is too large for "long" type
SDL_blit_A.c:227: warning: integer constant is too large for "long" type
[...]
The first attached patch (longlongfix.patch) tells gcc to really treat
those constants as unsigned long long and not long.
The second patch (nasinclude.patch) fixes an include problem I had while
compiling nas audio : when the <audio/audiolib.h> file lies in
/usr/X11R6/include, a -I/usr/X11R6/include option is needed or the file
isn't found.
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Sun, 21 Sep 2003 18:32:04 +0000 |
parents | e5bc29de3f0a |
children | 546f7c1eb755 |
line wrap: on
line source
.TH "SDL_LockSurface" "3" "Tue 11 Sep 2001, 23:01" "SDL" "SDL API Reference" .SH "NAME" SDL_LockSurface\- Lock a surface for directly access\&. .SH "SYNOPSIS" .PP \fB#include "SDL\&.h" .sp \fBint \fBSDL_LockSurface\fP\fR(\fBSDL_Surface *surface\fR); .SH "DESCRIPTION" .PP \fBSDL_LockSurface\fP sets up a surface for directly accessing the pixels\&. Between calls to \fBSDL_LockSurface\fP and \fBSDL_UnlockSurface\fP, you can write to and read from \fBsurface->\fBpixels\fR\fR, using the pixel format stored in \fBsurface->\fBformat\fR\fR\&. Once you are done accessing the surface, you should use \fBSDL_UnlockSurface\fP to release it\&. .PP Not all surfaces require locking\&. If \fBSDL_MUSTLOCK\fP(\fBsurface\fR) evaluates to \fB0\fR, then you can read and write to the surface at any time, and the pixel format of the surface will not change\&. .PP No operating system or library calls should be made between lock/unlock pairs, as critical system locks may be held during this time\&. .PP It should be noted, that since SDL 1\&.1\&.8 surface locks are recursive\&. This means that you can lock a surface multiple times, but each lock must have a match unlock\&. .PP .nf \f(CW \&. \&. SDL_LockSurface( surface ); \&. /* Surface is locked */ /* Direct pixel access on surface here */ \&. SDL_LockSurface( surface ); \&. /* More direct pixel access on surface */ \&. SDL_UnlockSurface( surface ); /* Surface is still locked */ /* Note: Is versions < 1\&.1\&.8, the surface would have been */ /* no longer locked at this stage */ \&. SDL_UnlockSurface( surface ); /* Surface is now unlocked */ \&. \&.\fR .fi .PP .SH "RETURN VALUE" .PP \fBSDL_LockSurface\fP returns \fB0\fR, or \fB-1\fR if the surface couldn\&'t be locked\&. .SH "SEE ALSO" .PP \fI\fBSDL_UnlockSurface\fP\fR ...\" created by instant / docbook-to-man, Tue 11 Sep 2001, 23:01