Fri, 16 Aug 2013 15:38:06 -0700 The keyboard text events should be sent after the key down events
Sam Lantinga <slouken@libsdl.org> [Fri, 16 Aug 2013 15:38:06 -0700] rev 7646
The keyboard text events should be sent after the key down events
Fri, 16 Aug 2013 15:35:10 -0700 Fixed bug 1876 - SDL_TEXTINPUT only returns '?' (0x3F) in event.text.text with Khmer language input
Sam Lantinga <slouken@libsdl.org> [Fri, 16 Aug 2013 15:35:10 -0700] rev 7645
Fixed bug 1876 - SDL_TEXTINPUT only returns '?' (0x3F) in event.text.text with Khmer language input Andreas The issue comes down to this line on MSDN: "TranslateMessage produces WM_CHAR messages only for keys that are mapped to ASCII characters by the keyboard driver." "WM_KEYDOWN and WM_KEYUP combinations produce a WM_CHAR or WM_DEADCHAR message. WM_SYSKEYDOWN and WM_SYSKEYUP combinations produce a WM_SYSCHAR or WM_SYSDEADCHAR message." Except for WM_CHAR, none of these messages are used in SDL. Hence TranslateMessage should be dropped entirely and proper handling be included in the WM_KEYDOWN event. Currently TranslateMessage is called for every message even if it must not be called in certain cases (like "An application should not call TranslateMessage if the TranslateAccelerator function returns a nonzero value."). WM_CHAR message handling should remain for external processes posting these messages - additionally, WM_UNICHAR should be added. I made a patch for src/video/windows/SDL_windowsevents.c that seems to work fine. It doesn't solve the "missing" composition for Khmer, but at least input for languages that cannot be mapped to ASCII characters (and for which IME is not used) will now work on Windows.
Fri, 16 Aug 2013 14:38:04 -0300 Android quirk:Some devices don't report GL_OES_framebuffer_object but support it
Gabriel Jacobo <gabomdq@gmail.com> [Fri, 16 Aug 2013 14:38:04 -0300] rev 7644
Android quirk:Some devices don't report GL_OES_framebuffer_object but support it
Fri, 16 Aug 2013 12:51:29 -0400 Patched to compile.
Ryan C. Gordon <icculus@icculus.org> [Fri, 16 Aug 2013 12:51:29 -0400] rev 7643
Patched to compile.
Fri, 16 Aug 2013 13:37:27 -0300 [Bug 2042] OpenGL ES renderer tries to load OES functions unconditionally
Gabriel Jacobo <gabomdq@gmail.com> [Fri, 16 Aug 2013 13:37:27 -0300] rev 7642
[Bug 2042] OpenGL ES renderer tries to load OES functions unconditionally Also, fail more gracefully when creating texture to avoid double free errors.
Fri, 16 Aug 2013 09:20:33 -0700 Fixed alpha composition when destination alpha is transparent.
Sam Lantinga <slouken@libsdl.org> [Fri, 16 Aug 2013 09:20:33 -0700] rev 7641
Fixed alpha composition when destination alpha is transparent. Jianyu Guan I found I make a big mistake that when dstA==0, I just simply let *dstp=*srcp and forgot to make dstRGB = srcRGB*srcA. The if consition "(*dstp & amask) == 0" in BlitRGBtoRGBPixelAlphaMMX and BlitRGBtoRGBPixelAlphaMMX3dNow should be removed.
Fri, 16 Aug 2013 06:59:19 -0700 Fixed alpha blending for the MMX blit functions
Sam Lantinga <slouken@libsdl.org> [Fri, 16 Aug 2013 06:59:19 -0700] rev 7640
Fixed alpha blending for the MMX blit functions I see the Remarks of function SDL_BlitSurface shows that "when SDL_BLENDMODE_BLEND, we have dstA = srcA + (dstA * (1-srcA))". however, I tested some pictures but the result implies "dstA=arcA" actually. I stepped into the source code, and found after I set SDL_BLENDMODE_BLEND for the source surface, the final blit function is BlitRGBtoRGBPixelAlphaMMX when I use SDL_BlitSurface on my computer. And I found these codes: else if (alpha == amask) { /* opaque alpha -- copy RGB, keep dst alpha */ *dstp = (*srcp & chanmask) | (*dstp & ~chanmask); The same code is used in BlitRGBtoRGBPixelAlphaMMX3DNOW and BlitRGBtoRGBPixelAlpha. So I think they still keep dst alpha. Best regards, Jianyu Guan
Wed, 14 Aug 2013 23:30:10 -0700 Fix bug 2034: replace printf by SDL_Log in tests; update loopwave VS solution: copy missing dependency
Andreas Schiffler <aschiffler@ferzkopp.net> [Wed, 14 Aug 2013 23:30:10 -0700] rev 7639
Fix bug 2034: replace printf by SDL_Log in tests; update loopwave VS solution: copy missing dependency
Mon, 12 Aug 2013 22:00:21 -0700 Don't print "unrecognized key" message for an X11 keycode of 0. This can happen with composed characters.
Sam Lantinga <slouken@libsdl.org> [Mon, 12 Aug 2013 22:00:21 -0700] rev 7638
Don't print "unrecognized key" message for an X11 keycode of 0. This can happen with composed characters.
Mon, 12 Aug 2013 19:18:48 -0700 Fixed the tag name for the SDL 2.0 release
Sam Lantinga <slouken@libsdl.org> [Mon, 12 Aug 2013 19:18:48 -0700] rev 7637
Fixed the tag name for the SDL 2.0 release
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 tip