Hi,
Key repeat rate: I noticed when porting to SDL 2.0 there wasn’t an API
to set this. A bit of web searching found me a list email from Sam
suggesting that it was preferable that this wasn’t in SDL 2.0, and
that perhaps users could use OS API to modify it (maybe I am
paraphrasing a little). I am unable to locate a suitable API for this
for Android. I was going to ignore it, but a user has been reporting
that the current repeat rate with his physical keyboard attached is
too slow.
Soft keyboards and applications wanting to get key presses. I have a
custom display with a text field where a user sees what they type on
other platforms, but when I pop up the soft keyboard all text entry
goes into the predictive input bar of the keyboard. Some keys do get
through, but not letters. I hear (or rather googled) if you have a
proper Android UI text field, you can set some arcane combination of
filtering settings that bypasses the predictive input. But I’ve got
custom game UI that does not have this option. There is of course the
system setting that disables predictive input, but that’s too much to
ask of the user.
Any insight would be appreciated, even if it’s just that any SDL-based
Android application just has to code custom solutions 
Cheers,
Richard.
Keyboard to android phone? I’m not sure you can ajust it. That speed may be
from the bluetooth. You didn’t say it was bluetooth. Is it? Since it was
not designed to have a keyboard work properly there could be an issue no
matter how you do it.On Sun, Jul 29, 2012 at 7:13 PM, Richard Tew <richard.m.tew at gmail.com>wrote:
Hi,
Key repeat rate: I noticed when porting to SDL 2.0 there wasn’t an API
to set this. A bit of web searching found me a list email from Sam
suggesting that it was preferable that this wasn’t in SDL 2.0, and
that perhaps users could use OS API to modify it (maybe I am
paraphrasing a little). I am unable to locate a suitable API for this
for Android. I was going to ignore it, but a user has been reporting
that the current repeat rate with his physical keyboard attached is
too slow.
Soft keyboards and applications wanting to get key presses. I have a
custom display with a text field where a user sees what they type on
other platforms, but when I pop up the soft keyboard all text entry
goes into the predictive input bar of the keyboard. Some keys do get
through, but not letters. I hear (or rather googled) if you have a
proper Android UI text field, you can set some arcane combination of
filtering settings that bypasses the predictive input. But I’ve got
custom game UI that does not have this option. There is of course the
system setting that disables predictive input, but that’s too much to
ask of the user.
Any insight would be appreciated, even if it’s just that any SDL-based
Android application just has to code custom solutions
Cheers,
Richard.
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
You could track keys with SDL_KEY_DOWN and UP events and manually do
repeats, however, I don’t know if Android would try and interfere with that.
-AlexOn Sun, Jul 29, 2012 at 8:13 PM, Richard Tew <richard.m.tew at gmail.com>wrote:
Hi,
Key repeat rate: I noticed when porting to SDL 2.0 there wasn’t an API
to set this. A bit of web searching found me a list email from Sam
suggesting that it was preferable that this wasn’t in SDL 2.0, and
that perhaps users could use OS API to modify it (maybe I am
paraphrasing a little). I am unable to locate a suitable API for this
for Android. I was going to ignore it, but a user has been reporting
that the current repeat rate with his physical keyboard attached is
too slow.
Soft keyboards and applications wanting to get key presses. I have a
custom display with a text field where a user sees what they type on
other platforms, but when I pop up the soft keyboard all text entry
goes into the predictive input bar of the keyboard. Some keys do get
through, but not letters. I hear (or rather googled) if you have a
proper Android UI text field, you can set some arcane combination of
filtering settings that bypasses the predictive input. But I’ve got
custom game UI that does not have this option. There is of course the
system setting that disables predictive input, but that’s too much to
ask of the user.
Any insight would be appreciated, even if it’s just that any SDL-based
Android application just has to code custom solutions
Cheers,
Richard.
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org