Mercurial > sdl-ios-xcode
view docs/man3/SDL_LockSurface.3 @ 4391:07b330419439 SDL-1.2
Fixed bug #849 some more:
Tim Angus 2009-11-26 14:41:04 PST
Fix to the cursor not being responsive when the app doesn't have
SDL_APPINPUTFOCUS
The problems with the directx driver are similar to the ones I introduced in
the windib driver with r4478. Basically if the application did not have focus,
the mouse position is not updated. It's not really that the mouse cursor was
invisible, it's that it is stuck underneath another window where you can't see
it. This behaviour predates my r4478 changes and is the reason I unwittingly
broke the windib driver as I had been replicating the way the directx driver
deals with focus. Prior to r4478 the directx driver could not be used in
windowed mode, so the broken focusing would not have actually been observable.
Anyway, the attached patch makes the directx driver behaves like the windib
driver in terms of focus.
Time for 1.2.15? ;)
I've added an additional change of moving the calls to WIN_GrabInput that are
made on WM_ACTIVATE messages so that they only occur when the state is
SDL_APPINPUTFOCUS. When a fullscreen application is minimised using alt-tab, it
still receives WM_ACTIVATE messages when other applications are selected. If
WIN_GrabInput is called when the SDL application doesn't have input focus, bad
things happen; it shouldn't be being called at all.
I've also added a line to make sure that SDL_APPMOUSEFOCUS state is dropped
when the application is minimised following an alt-tab.
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Fri, 11 Dec 2009 15:24:53 +0000 |
parents | 1238da4a7112 |
children |
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