Sat, 17 Aug 2013 17:04:14 -0700Fixed for consistency with the other platforms
Sam Lantinga [Sat, 17 Aug 2013 17:04:14 -0700] rev 7650
Fixed for consistency with the other platforms

Sat, 17 Aug 2013 18:07:29 -0400auto init the ticks if the GetTicks and the like methods are called before SDL_Init().. This prevents annoying game bugs such as caching SDL_GetPerformanceFrequency in a static initializer
Edward Rudd [Sat, 17 Aug 2013 18:07:29 -0400] rev 7649
auto init the ticks if the GetTicks and the like methods are called before SDL_Init().. This prevents annoying game bugs such as caching SDL_GetPerformanceFrequency in a static initializer

Sat, 17 Aug 2013 09:54:30 -0700Do full state initialization in D3D_Reset(), this fixes blend mode issues when resizing the window on Windows 8.
Sam Lantinga [Sat, 17 Aug 2013 09:54:30 -0700] rev 7648
Do full state initialization in D3D_Reset(), this fixes blend mode issues when resizing the window on Windows 8.

Fri, 16 Aug 2013 17:50:44 -0700Fixed windows build
Sam Lantinga [Fri, 16 Aug 2013 17:50:44 -0700] rev 7647
Fixed windows build

Fri, 16 Aug 2013 15:38:06 -0700The keyboard text events should be sent after the key down events
Sam Lantinga [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 -0700Fixed bug 1876 - SDL_TEXTINPUT only returns '?' (0x3F) in event.text.text with Khmer language input
Sam Lantinga [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 -0300Android quirk:Some devices don't report GL_OES_framebuffer_object but support it
Gabriel Jacobo [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 -0400Patched to compile.
Ryan C. Gordon [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 [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 -0700Fixed alpha composition when destination alpha is transparent.
Sam Lantinga [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.