Mercurial > sdl-ios-xcode
view README.CVS @ 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 | 37e3ca9254c7 |
| children | ec659230eaac |
line wrap: on
line source
The latest development version of SDL is available via CVS: cvs -d :pserver:guest@libsdl.org:/home/slouken/libsdl.org/cvs login # No password, so just hit enter when prompted for a password cvs -d :pserver:guest@libsdl.org:/home/slouken/libsdl.org/cvs checkout SDL When you check a fresh copy of SDL out of CVS, you need to generate the files used by make by running the "autogen.sh" script, which will run aclocal, automake, autoconf and then run configure. There is a web interface to cvs at http://www.libsdl.org/cgi/cvsweb.cgi