Mercurial > sdl-ios-xcode
view src/video/Xext/README @ 561:4bcf7dd06c47
Date: Sat, 14 Dec 2002 13:33:05 -0500
From: Darrell Walisser
Subject: Re: crash in SDL / OSX
> Yes, compose keys and other "dead" keys should have unicode 0.
> As a hack, if you get multiple composed characters, you can send the
> sequence with a valid unicode and a keysym of 0. It's because of
> things like this that I'm separating the key and char events in SDL 2.0
I've done this and here's the patch.
author | Sam Lantinga <slouken@libsdl.org> |
---|---|
date | Sun, 15 Dec 2002 09:09:31 +0000 |
parents | eadc0746dfaf |
children | b87d8d4c205d |
line wrap: on
line source
The reason these libraries are built outside of the standard XFree86 tree is so that they can be linked as shared object code directly into SDL without causing any symbol collisions with code in the application. You can't link static library code into shared libraries on non-x86 Linux platforms. Since these libraries haven't become standard yet, we'll just include them directly.