We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 4781 - Feature request: please allow disabling virtual keyboard on Android even when using SDL_StartTextInput()
Summary: Feature request: please allow disabling virtual keyboard on Android even when...
Status: NEW
Alias: None
Product: SDL
Classification: Unclassified
Component: events (show other bugs)
Version: 2.0.10
Hardware: x86_64 Android (All)
: P2 enhancement
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-01 14:06 UTC by Ellie
Modified: 2019-09-01 14:06 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ellie 2019-09-01 14:06:14 UTC 
Here it was described that SDL_StartTextInput() is now tied together with showing the virtual keyboard: https://discourse.libsdl.org/t/on-screen-keyboard-change/19216

However, I now have the following problem:

- I have a custom cross-platform simplified virtual keyboard written in SDl2/in-app to have one for use with xbox controller (for entering high score abbreviations etc with just the controller)

- Since I want things to work with e.g. xbox controllers on Android too I HAVE to use this custom keyboard on Android I think. But even otherwise I would also still want to, for keeping it uniform and since nobody will enter like emails or novels where full international input would be super important anyway

- However, I also want to support enabling the hardware keyboard at the same time for user convenience, and I want things like ':' to work. And this can differ depending on layout and may or may not involve checking the shift modifier etc., so not sure how practical this is to do manually. I'd rather use the text input event, but that would bring up the second native android virtual keyboard...

Combined this means my best solution appears to be to use SDL_StartTextInput() but WITHOUT showing the native/android virtual keyboard, so exactly what apparently was removed from SDL2 in 2012.

Is there any chance this separation can be reintroduced in some form? Maybe a hint would work to just disable ever bringing up the virtual keyboard altogether?