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

App keyboard #1

Merged
merged 8 commits into from
Jan 20, 2024
Merged

App keyboard #1

merged 8 commits into from
Jan 20, 2024

Conversation

amwatson
Copy link
Owner

This is a big of a hack: Some 3DS titles expect a system keyboard.

Normally in Citra android, an edittext is used to pull up the android keyboard to use as keyboard input. However, on Quest, a window management "bug" (in quotes because this behavior is probably undocumented) prevents the same technique from working (see note in vr_keyboard.xml)

I don't like that this completely fragments the codebase, and it might be a little buggy, but it does open CitraVR up to a number of important titles that rely on this behavior.

Some limitations:

  • Keyboard may reject input based on an error, and that error isn't being
    visualized (it is logged).
  • No non-english keyboard support
  • I'm not including all symbols right now

@amwatson amwatson merged commit 11fea29 into master Jan 20, 2024
3 of 22 checks passed
@amwatson amwatson deleted the app_keyboard branch January 20, 2024 09:27
@amwatson
Copy link
Owner Author

oh, additonally:

  1. when the UI closes, the menu bar is still active, so users will have to close that. this will probably annoy people
  2. the upside of doing the keyboard this way is that users should be able to use external keyboards if they want to

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

Successfully merging this pull request may close these issues.

1 participant