This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

• patch (input_flag.patch, text/plain, 2014-10-05 11:00:55 +0000, 510 bytes)

Reported in version: HG 2.1
Reported for operating system, platform: Linux, All

Comments on the original bug report:

On 2014-10-05 11:00:55 +0000, Jonas Kulla wrote:

Created attachment 1889
patch

X11 backend of window creation code (SDL_x11window.c:297) decides based on this flag whether to call SDL_SetKeyboardFocus, and I need this to be called because I use multiple windows and can't differentiate key events based on the windowID otherwise.

On 2014-11-03 18:17:39 +0000, Jonas Kulla wrote:

bump.

On 2017-08-09 05:32:20 +0000, Ryan C. Gordon wrote:

(Sorry if you get a lot of copies of this email, we're touching dozens of bug reports right now.)

Tagging a bunch of bugs as target-2.0.6.

This means we're in the final stretch for an official SDL 2.0.6 release! These are the bugs we really want to fix before shipping if humanly possible.

That being said, we don't promise to fix them because of this tag, we just want to make sure we don't forget to deal with them before we bless a final 2.0.6 release, and generally be organized about what we're aiming to ship. After some debate, we might just remove this tag again and deal with it for a later release.

Hopefully you'll hear more about this bug soon. If you have more information (including "this got fixed at some point, nevermind"), we would love to have you come add more information to the bug report when you have a moment.

Thanks!
--ryan.

On 2017-08-09 23:25:58 +0000, Sam Lantinga wrote:

What the X11 code is actually doing is checking to see if the window really has focus, and calling SDL_SetKeyboardFocus() if that's the case.

What should be happening is the fact that you're mapping the windows should cause the window manager to give focus to one of your windows and SDL should catch that event and assign that window focus internally.

Since that doesn't appear to be happening, that seems to be a bug in the window manager event detection for new windows. Can you please post a minimal example that reproduces this problem so we can investigate more thoroughly?

Thanks!