Mercurial > sdl-ios-xcode
view README.Qtopia @ 3978:b966761fef6c SDL-1.2
Significantly improved XIM support.
Fixes Bugzilla #429.
Selected notes from the patch's README:
= FIXES =
This patch fixes the above issues as follows.
== X11 events ==
Moved XFilterEvent just after XNextEvent so that all events are passed
to it. Also, XFilterEvent will receive masks indicated by IM through
XNFilterEvents IC value as well as masks surpplied by SDL.
X11_KeyRepeat is called between XNextEvent and XFilterEvent, after
testing an event is a KeyRelease. I'm not 100% comfortable to do so,
but I couldn't find a better timing to call it, and use of the
function is inevitable.
== Xutf8LookupString ==
Used a longer buffer to receive UTF-8 string. If it is insufficient,
a dynamic storage of the requested size will be allocated. The
initial size of the buffer is set to 32, because the Japanese text
converted from the most widely used benchmark key sequence for
Japanese IM, "WATASHINONAMAEHANAKANODESU." has ten Japanese characters
in it, that occupies 30 bytes when encoded in UTF-8.
== SDL_keysym.unicode ==
On Windows version of SDL implementation, SDL_keysym.unicode stores
UTF-16 encoded unicode characters, one UTF-16 encoding unit per an SDL
event. A Unicode supplementary characters are sent to an application
as two events. (One with a high surrogate and another with a low
surrogate.) The behavior seems reasonable since it is upward
compatible with existing handling of BMP characters.
I wrote a UTF-8 to UTF-16 conversion function for the purpose. It is
designed with the execution speed in mind, having a minimum set of
features that my patch requires.
author | Ryan C. Gordon <icculus@icculus.org> |
---|---|
date | Mon, 25 Jun 2007 19:58:32 +0000 |
parents | 2c5d4c22a2ac |
children |
line wrap: on
line source
============================================================================== Using the Simple DirectMedia Layer with Qtopia/OPIE ============================================================================== ============================================================================== I. Setting up the Qtopia development environment. This document will not explain how to setup the Qtopia development environment. That is outside the scope of the document. You can read more on this subject in this excellent howto: http://www.zauruszone.com/howtos/linux_compiler_setup_howto.html ============================================================================== II. Building the Simple DirectMedia Layer libraries using the arm cross-compiler This is somewhat tricky since the name of the compiler binaries differ from the standard. Also you should disable features not needed. The command below works for me. Note that it's all one line. You can also set the NM, LD etc environment variables separately. NM=arm-linux-nm LD=arm-linux-ld CC=arm-linux-gcc CXX=arm-linux-g++ RANLIB=arm-linux-ranlib AR=arm-linux-ar ./configure --enable-video-qtopia --disable-video-dummy --disable-video-fbcon --disable-video-dga --disable-arts --disable-esd --disable-alsa --disable-cdrom --disable-video-x11 --disable-nasm --prefix=/opt/Qtopia/sharp/ arm-unknown-linux-gnu One thing to note is that the above configure will include joystick support, even though you can't have joysticks on the Zaurus. The reason for this is to avoid link / compile / runtime errors with applications that have joystick support. ============================================================================== III. Building the Simple DirectMedia Layer test programs: After installing, making sure the correct sdl-config is in your path, run configure like this: NM=arm-linux-nm LD=arm-linux-ld CC=arm-linux-gcc CXX=arm-linux-g++ AR=arm-linux-ar ./configure arm-unknown-linux-gnu ============================================================================== IV. Application porting notes One thing I have noticed is that applications sometimes don't exit correctly. Their icon remains in the taskbar and they tend to relaunch themselves automatically. I believe this problem doesn't occur if you exit your application using the exit() method. However, if you end main() with 'return 0;' or so, this seems to happen. Also note that when running in landscape mode - i.e requesting a window that is HEIGHT pixels wide and WIDTH pixels high, where WIDTH and HEIGHT normally is 240 and 320 - the image is blitted so that the hardware buttons are on the left side of the display. This might not always be desirable but such is the code today. ============================================================================== V. Enjoy! :) If you have a project you'd like me to know about, or want to ask questions, go ahead and join the SDL developer's mailing list by sending e-mail to: sdl-request@libsdl.org and put "subscribe" into the subject of the message. Or alternatively you can use the web interface: http://www.libsdl.org/mailman/listinfo/sdl ============================================================================== VI. What is supported: Keyboard (Sharp Zaurus) Hardware buttons Stylus input (mouse) Video. Allows fullscreen both in portrait mode (up to WIDTHxHEIGHT size window) and in landscape mode (up to HEIGHTxWIDTH). All other SDL functionality works like a normal Linux system (threads, audio etc). -- David Hedbor <david@hedbor.org> http://david.hedbor.org/ http://eongames.com/