Page 1 of 1

Android messaging keyboard

PostPosted: 13 Dec 2018, 20:03
by eltomito
Hi! Bitchin' 'bout da droid again...

TL;DR 1) Move the messaging keyboard to the bottom of the screen
2) Add left/right arrows or the possibility to move the cursor by tapping in the message box

I've been trying to get used to the STK Android keyboard but I'm still much slower than people who I assume are typing on a real keyboard.
I think it could be helped by moving the on-screen keyboard to the bottom of the display, because then you would see what you're typing and could correct mistakes immediately as opposed to obscuring the message box with your hands.

It would also help a lot to add a cursor that you can move around the message box somehow, either with some new left/right keys or by clicking in the message box.
Even if the cursor is invisible and you make it possible to move it by clicking somewhere, it will make messaging much simpler.

The problem is that often, I type something like "are u humamorbot?" which is pretty incomprehensible at the first glance. But just adding the two missing spaces makes it a lot easier to understand and changing the 'm' into an 'n' makes it perfect. But to do that now, I have to delete 6 characters and type them again on a keyboard that isn't all that easy to use. So, there.

And thanks for the whole global gameplay. It's totally cool!

Re: Android messaging keyboard

PostPosted: 13 Dec 2018, 21:01
by deve
Thanks for your feedback.

Good keyboard support requires a lot of work. I like the way how SDL2 is doing it. It uses system screen keyboard and you choose which window region is interesting for you, so that it "moves" whole window and edit box is always visible. But it's not possible to do with pure c++ or jvm. You need to handle all input event in java and make an interface to communicate with STK, so that whole CIrrDeviceAndroid would have to be rewritten.

In current beta package you can edit config.xml and set screen_keyboard_mode="3" to enable system keyboard support. It's a very quick hack though and complex characters and voice messages won't work.

And the STK keyboard is displayed on top/bottom depending on edit box position, to make sure that it's always visible.

Re: Android messaging keyboard

PostPosted: 01 Jan 2019, 12:59
by eltomito
Happy New Year!
deve {l Wrote}:In current beta package you can edit config.xml and set screen_keyboard_mode="3" to enable system keyboard support.

What exactly does the option look like? Looking at config.xml, it should be something like <screen-keyboard mode="3"\> but there's nothing like that in there.
deve {l Wrote}:And the STK keyboard is displayed on top/bottom depending on edit box position, to make sure that it's always visible.

Yeah. I think it would really help to move the edit box to the top of the screen then, above the chat window, to make the keyboard pop up at the bottom. Right now, typing is hell on Earth. I thought I'd get used to it after a couple of days but no. When I try to chat with people, I feel like trying to play soccer for Real Madrid in a wheelchair. :D

Re: Android messaging keyboard

PostPosted: 28 May 2019, 03:34
by benau
You can try the https://play.google.com/store/apps/deta ... t.stk_beta can see if it good for you

Re: Android messaging keyboard

PostPosted: 28 May 2019, 19:18
by eltomito
Thanks for the new keyboard! The top placement is much better. But I how do you type an exclamation mark ! With it?!

Re: Android messaging keyboard

PostPosted: 29 May 2019, 02:13
by benau
You should see your daily keyboard in stk now? (so you type the same?)

https://www.youtube.com/watch?v=uWjonSUN98I

It's not possible to change native keyboard position, or if u are using gboard you can enable floating keyboard (in the video, press ... in Google bar, there is an option for keyboard type)

Re: Android messaging keyboard

PostPosted: 29 May 2019, 14:06
by eltomito
benau {l Wrote}:You should see your daily keyboard in stk now? (so you type the same?)


I see it now and it's great! Thank you!!!!
My stk beta wasn't up to date which was why I didn't see it before.