Sun, 08 Apr 2012 03:59:36 -0400 I think this may fix the altivec blitters.
Sam Lantinga <slouken@libsdl.org> [Sun, 08 Apr 2012 03:59:36 -0400] rev 6304
I think this may fix the altivec blitters.
Tue, 28 Feb 2012 21:58:36 -0500 Fixed bug 1429 - Compiling static library with -arch fails when linking showimage
Sam Lantinga <slouken@libsdl.org> [Tue, 28 Feb 2012 21:58:36 -0500] rev 6303
Fixed bug 1429 - Compiling static library with -arch fails when linking showimage We no longer need this ancient hack and it's causing problems when building shared libraries against SDL.
Sat, 04 Feb 2012 00:13:21 +1300 Make mouse relative mode save the original co-ordinates to restore them
Wim Looman <ghostunderscore@gmail.com> [Sat, 04 Feb 2012 00:13:21 +1300] rev 6302
Make mouse relative mode save the original co-ordinates to restore them properly.
Fri, 03 Feb 2012 23:53:51 +1300 Change SDL_SetCursor to set the cursor back to the default cursor when the
Wim Looman <ghostunderscore@gmail.com> [Fri, 03 Feb 2012 23:53:51 +1300] rev 6301
Change SDL_SetCursor to set the cursor back to the default cursor when the window is unfocused.
Fri, 03 Feb 2012 23:08:48 +1300 Fix null reference exception.
Wim Looman <ghostunderscore@gmail.com> [Fri, 03 Feb 2012 23:08:48 +1300] rev 6300
Fix null reference exception. Occurred when using relative mouse mode without a focused window.
Mon, 20 Feb 2012 23:54:33 -0500 Fixed bug 1423 - Finger touch events don't report pressure
Sam Lantinga <slouken@libsdl.org> [Mon, 20 Feb 2012 23:54:33 -0500] rev 6299
Fixed bug 1423 - Finger touch events don't report pressure Philip Taylor 2012-02-19 08:34:52 PST SDL_touch.c never actually uses the 'pressurein' arguments to SDL_SendFingerDown/SDL_SendTouchMotion, so it doesn't report the real pressure. Also it uses touch->pressureres which is never initialised. Also it fails to initialise some fields of event.tfinger for certain events, so applications might try to use bogus data. The attached patch seems to be enough to produce generally sensible output on Android.
Mon, 20 Feb 2012 23:51:53 -0500 Fixed bug 1426 - SDL_SemWaitTimeout returns -1 and sets error instead of SDL_MUTEX_TIMEDOUT on time out
Sam Lantinga <slouken@libsdl.org> [Mon, 20 Feb 2012 23:51:53 -0500] rev 6298
Fixed bug 1426 - SDL_SemWaitTimeout returns -1 and sets error instead of SDL_MUTEX_TIMEDOUT on time out deraj 2012-02-19 19:01:08 PST Fix to treat ETIMEDOUT as a time out instead of an error (and update the test)
Mon, 20 Feb 2012 23:51:08 -0500 Fixed bug 1426 - SDL_SemWaitTimeout returns -1 and sets error instead of SDL_MUTEX_TIMEDOUT on time out SDL-1.2
Sam Lantinga <slouken@libsdl.org> [Mon, 20 Feb 2012 23:51:08 -0500] rev 6297
Fixed bug 1426 - SDL_SemWaitTimeout returns -1 and sets error instead of SDL_MUTEX_TIMEDOUT on time out deraj 2012-02-19 19:01:08 PST Fix to treat ETIMEDOUT as a time out instead of an error (and update the test)
Mon, 20 Feb 2012 23:37:57 -0500 Add OpenGL 3.X context creation support
Sam Lantinga <slouken@libsdl.org> [Mon, 20 Feb 2012 23:37:57 -0500] rev 6296
Add OpenGL 3.X context creation support Matthias Bentrup 2011-10-30 03:58:24 PDT I've updated the context creation patch to include the bugfixes by Martin Schreiber and also included a profile bit to request a ES2 compatible profile. The wgl context creation may use 2 call to wglChoosePixelFormat if no acceleration attribute is selected, this should work around a bug with buggy AMD drivers (see #1254).
Mon, 20 Feb 2012 20:56:52 -0500 Fixed bug 1424 - Handling of alpha channel in Altivec accelerated blit functions
Sam Lantinga <slouken@libsdl.org> [Mon, 20 Feb 2012 20:56:52 -0500] rev 6295
Fixed bug 1424 - Handling of alpha channel in Altivec accelerated blit functions evilbite 2012-02-19 09:38:21 PST There is only one Altivec accelerated blit function (ConvertAltivec32to32_prefetch() or ConvertAltivec32to32_noprefetch(), depending on the CPU used) that is supposed to handle all alpha combinations. This works as follows for every pixel line: 1. Blit single pixels until an aligned address is reached 2. Accelerated blit as far as possible 3. Blit single remaining pixels Part 2. is set up correctly to handle different combinations of the alpha channels of the participating surfaces. Parts 1. and 3. only do a simple copy of all the pixel's components from souce to destination. But when the source surface has no alpha channel (Amask is 0, e.g. the video surface) the surface's alpha value must be used instead. Otherwise crap (uninitialized data) is being copied to the destiniation's alpha channel. The attached patch is a quick'n'dirty solution to the problem. A more sophisticated solution might require separate functions for different combinations of the alpha channels of the participating surfaces.
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip