author Sam Lantinga <>
Wed, 03 Oct 2012 20:49:16 -0700
changeset 6555 f2c03c06d987
parent 1946 103760c3a5dc
child 6987 7084af936d82
permissions -rw-r--r--
Fixed bug 1614 - SDL for Android does not implement TextInput API

Andrey Isakov 2012-10-03 08:30:25 PDT

I've found out in the process of porting one OS project to Android/SDL2 that
there is no support for TextInput events/APIs on Android.
So I implemented some kind of initial support of that feature, and at the very
least it seems to work fine with latin chars input with soft and hardware
keyboards on my Moto Milestone2. I've also tried playing around with more
complex IMEs, like japanese, logging the process and it seemed to work too. I'm
not sure since the app itself I am working on does not have support for
non-latin input.

The main point of the patch is to place a fake input view in the region
specified by SDL_SetTextInputRect and create a custom InputConnection for it.
The reason to make it a separate view is to support Android's pan&scan on input
feature properly. For details please refer to
Even though the manual states that SetTextInputRect is used to determine the
IME variants position, I thought this would be a proper use for this too.
     2 * Porting To A New Platform
     4   The first thing you have to do when porting to a new platform, is look at
     5 include/SDL_platform.h and create an entry there for your operating system.
     6 The standard format is __PLATFORM__, where PLATFORM is the name of the OS.
     7 Ideally SDL_platform.h will be able to auto-detect the system it's building
     8 on based on C preprocessor symbols.
    10 There are two basic ways of building SDL at the moment:
    12 1. The "UNIX" way:  ./configure; make; make install
    14    If you have a GNUish system, then you might try this.  Edit,
    15    take a look at the large section labelled:
    16 	"Set up the configuration based on the target platform!"
    17    Add a section for your platform, and then re-run and build!
    19 2. Using an IDE:
    21    If you're using an IDE or other non-configure build system, you'll probably
    22    want to create a custom SDL_config.h for your platform.  Edit SDL_config.h,
    23    add a section for your platform, and create a custom SDL_config_{platform}.h,
    24    based on SDL_config.h.minimal and
    26    Add the top level include directory to the header search path, and then add
    27    the following sources to the project:
    28 	src/*.c
    29 	src/audio/*.c
    30 	src/cdrom/*.c
    31 	src/cpuinfo/*.c
    32 	src/events/*.c
    33 	src/file/*.c
    34 	src/joystick/*.c
    35 	src/stdlib/*.c
    36 	src/thread/*.c
    37 	src/timer/*.c
    38 	src/video/*.c
    39 	src/audio/disk/*.c
    40 	src/audio/dummy/*.c
    41 	src/video/dummy/*.c
    42 	src/joystick/dummy/*.c
    43 	src/cdrom/dummy/*.c
    44 	src/thread/generic/*.c
    45 	src/timer/dummy/*.c
    46 	src/loadso/dummy/*.c
    49 Once you have a working library without any drivers, you can go back to each
    50 of the major subsystems and start implementing drivers for your platform.
    52 If you have any questions, don't hesitate to ask on the SDL mailing list:
    55 Enjoy!
    56 	Sam Lantinga				(