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

Touch focus events #35

Open
curiousdannii opened this issue Aug 12, 2017 · 5 comments
Open

Touch focus events #35

curiousdannii opened this issue Aug 12, 2017 · 5 comments

Comments

@curiousdannii
Copy link
Contributor

curiousdannii commented Aug 12, 2017

Currently in Quixe, you must tap the input box precisely in order to bring up the soft keyboard. It would probably be better to allow the user to tap anywhere in a window to focus the input (compare with Parchment which does this.)

If the input is already focused, tapping the window elsewhere will hide the keyboard and then show it again. This is far from ideal! Tapping the window should either not affect the soft keyboard, or it should hide the keyboard. It may not be possible to do the first, so perhaps tapping the window could toggle the keyboard on and off.

@erkyrath
Copy link
Owner

We'd have to test how this affects all the other things you can do by tapping a web page, such as selecting and scrolling.

@nebocamin
Copy link

I am not sure if it fits into this issue.

the inform 7 line "pause the game;" is waiting for an event that you can't do with android virtual keyboard for example. So you will stuck forever.
But "wait for any key;" is working.

@curiousdannii
Copy link
Contributor Author

That would be because keyboard input is not currently working: it returns some invalid keycode number, which will work for the "wait for any key" phrase, but not the "pause the game" phrase which waits specifically for the space key.

@cibersheep
Copy link

cibersheep commented Jan 19, 2018

This is an interesting issue.

  1. I don't know if it's easy to differentiate the input. A dirty hack could be, convert the «press SPACE key» into a link.
    or
  2. Searching a bit, I've found that this. Even if I don't use Android nor iOS, on Ubuntu Touch is also the same behaviour.
    Would be possible to use textInput as a workaround?

Note: keyup is 229 but in the screenshot is 175 (the button I pressed to make the screenshot :D )
imatge

@cibersheep
Copy link

cibersheep commented Jan 30, 2018

I got a solution! It was easier than I thought. I was obsessed with ev.wich and similar and the answer is the actual text.
So in evhan_input_char_keydown I created a new case 229: res=$("input").val()[0]; that easy. It took me two days

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

4 participants