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 3187 - SDL_StartTextInput() doesn't show up keyboard when it's called immediately after SDL_StopTextInput().
Summary: SDL_StartTextInput() doesn't show up keyboard when it's called immediately af...
Status: RESOLVED INVALID
Alias: None
Product: SDL
Classification: Unclassified
Component: events (show other bugs)
Version: 2.0.3
Hardware: All Android (All)
: P2 normal
Assignee: Sylvain
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-21 01:01 UTC by Hak Matsuda
Modified: 2018-12-30 15:18 UTC (History)
1 user (show)

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 Hak Matsuda 2015-11-21 01:01:29 UTC 
On Android, SDL_StartTextInput() doesn't show up keyboard when it's called immediately after SDL_StopTextInput().
When the issue happens, SDL_IsTextInputActive() still thinks an input session is going on.

Repro step:
1) Show SW keyboard by SDL_StartTextInput().
2) Invoke SDL_StopTextInput() to hide keyboard.
3) Call SDL_StartTextInput() before SW keyboard is hidden completely.
Comment 1 Ryan C. Gordon 2015-12-29 06:58:12 UTC 
I don't have an Android environment to test this at the moment, but it's possible that Android refuses to reshow the keyboard before the hiding animation completes.

It's strange that SDL_IsTextInputActive() returns SDL_TRUE, though, since it checks for something that SDL_StopTextInput() should have disabled:

    https://hg.libsdl.org/SDL/file/bbe9ef8c2ecb/src/video/SDL_video.c#l3416

Maybe this has changed recently in SDL, I don't know. Was this happening with SDL 2.0.3, or a newer version from revision control?

--ryan.
Comment 2 Sylvain 2017-08-14 09:11:32 UTC 
related to bug 3186
Comment 3 Sylvain 2018-12-30 15:16:53 UTC 
I've tried and couldn't reproduce it. Maybe it has been fixed in the meantime.

(Marked as invalid)
Comment 4 Sylvain 2018-12-30 15:18:15 UTC 
Please re-open if you still think this occurs!