Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SwiftKey: word suggestion bar missing #50

Open
cobra opened this issue Jul 19, 2012 · 4 comments
Open

SwiftKey: word suggestion bar missing #50

cobra opened this issue Jul 19, 2012 · 4 comments

Comments

@cobra
Copy link

cobra commented Jul 19, 2012

When using the SwiftKey keyboard in irssiconnectbot, the word suggestion bar is missing.
Swype is working correctly with its suggestion bar showing up.
I can't tell whether this is a SwiftKey issue or not. Is there anything special in irssiconnectbot about the keyboards?

@lizsugar
Copy link
Contributor

If you tap on the terminal screen you should see a row of icons appear briefly. Go ahead and tap the one that looks like an empty box. This will bring up an Android TextEntry field wherein the SwiftKey predictions will work.

@cobra
Copy link
Author

cobra commented Jul 20, 2012

that's even more annoying.

@lizsugar
Copy link
Contributor

As I see it, it is two fold:

  1. Normally, the keyboard is told what type of field it is sending its characters to, and certain types will enable prediction. If you notice, the default Android keyboard will also not display predictions in IRSSI ConnectBot. This is because there is no EditText field normally, and characters are intercepted directly off of the keyboard.
  2. Swype and TouchPal, for example, don't seem to honor those distinctions however, and thus will happily display their predictions at all times. This is probably because they don't send their information character by character, but instead as a whole word at a time, thus indicating that they do all of their spell checking and prediction before the word is even sent out of the keyobard. SwiftKey, on the other hand, operates on a word while that word is in the text field. If there is no text field for it to interact with, then it does not know there is a word.

With what I mentioned earlier, there is an EditText that can be used to enable prediction, and as such it feels, to me, to be a pretty solid work around for the situation.

(Actual developers: If I got any of this wrong, please feel free to correct me :) )

@kipe
Copy link

kipe commented Sep 6, 2012

IMO the TextEntry -field should stick once it's opened, with closing it being possible with the back key. At the moment the behaviour is quite frustrating, as it closes after each sent message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants