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

Windows: No way to tell whether SDL_KEY* events was trapped by the IMs #1737

Closed
SDLBugzilla opened this issue Feb 10, 2021 · 1 comment
Closed

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

Reported in version: 2.0.3
Reported for operating system, platform: Windows (All), x86

Comments on the original bug report:

On 2015-01-07 14:53:54 +0000, Kengo Ide wrote:

In the Windows backend of SDL 2.0.3, SDL is posting keyboard events which comes with VK_PROCESSKEY code to the SDL application as well as other virtual key codes. By the time applications receive them, those events was already processed by IME, typically to allow users to manipulate it, such as choosing candidates by arrow keys and submitting text by the enter key. An application that enables text input API would also have interest to these keys to implement their text editing function, so it will be a kind of weird behaviour, since key inputs that users meant to control IME will somehow also affects the underlying application.

As it seems that the SDL doesn't have any API to differentiate these key events, there is no way to implement East Asian text input correctly.

This issue also reported in the forum by a developer named ancientcc.
According to him, SDL1 didn't send trapped key events to the application.
https://forums.libsdl.org/viewtopic.php?p=44956&sid=04e7eb76a28229818b3c0de5f926434b

@slouken
Copy link
Collaborator

slouken commented Nov 4, 2023

I believe this is fixed in #5398, please reopen this if that's not the case.

@slouken slouken closed this as completed Nov 4, 2023
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

2 participants