Mercurial > sdl-ios-xcode
view docs/man3/SDL_GetError.3 @ 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 | e5bc29de3f0a |
children | 546f7c1eb755 |
line wrap: on
line source
.TH "SDL_GetError" "3" "Tue 11 Sep 2001, 23:00" "SDL" "SDL API Reference" .SH "NAME" SDL_GetError\- Get SDL error string .SH "SYNOPSIS" .PP \fB#include "SDL/SDL\&.h" .sp \fBchar *\fBSDL_GetError\fP\fR(\fBvoid\fR); .SH "DESCRIPTION" .PP \fBSDL_GetError\fP returns a NULL terminated string containing information about the last internal SDL error\&. .SH "RETURN VALUE" .PP \fBSDL_GetError\fP returns a string containing the last error\&. ...\" created by instant / docbook-to-man, Tue 11 Sep 2001, 23:00