parent 88580fa6c549
author Edward Rudd <urkle@outoforder.cc> 1350500791 14400
committer Edward Rudd <urkle@outoforder.cc> 1350500791 14400
revision 6592
branch default
use different rpath so SDL2.framework will live in the bundle's Framework folder
parent 7925f0f43dc4
author Edward Rudd <urkle@outoforder.cc> 1350500747 14400
committer Edward Rudd <urkle@outoforder.cc> 1350500747 14400
revision 6591
branch default
A few fixes to the SDL framework plist
- correct version number
- remove CFBundleExecutable
- correct CFBundleIdentifier
The OpenBSD case is puzzling - it's complaining about symbols in the C library. Do we need to explicitly link with -lc for shared libraries on OpenBSD?
The BeOS case is legitimate, it's calling back into the application code to initialize BeApp if it isn't already initialized.
Our new X11 window was being created with the TrueColor attribute, and trying to set the gamma
on that would fail. This change checks for the visual_info extension, and uses that to ask for
DirectColor if available.
The nVidia driver requires XInitThreads to be called for it to work in multithreaded mode. Sam also
says that the overhead for this is small enough that it should just be done by default at this point.
If this causes issues, we can add a hint later to enable / disable this call.
This was needed to get X11_SetWindowGammaRamp() working. Sam points out that there is an issue right now where
colormaps will only work with fullscreen windows, and we may want to set this when getting input focus for
windowed apps.
Because it's so broken, I'm going to disable XRandR by default. You can still enable it via environment variable or application hint (SDL_HINT_VIDEO_X11_XRANDR)
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
http://android-developers.blogspot.com/2009/04/updating-applications-for-on-screen.html
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.
