SDL/GLFW text input events reported to both keyPressEvent() and textInputEvent() about magnum-integration HOT 4 OPEN

Hi!

coincidentally, we were discussing this exact issue yesterday on the Gitter channel. The problem is that, for text input, SDL2 and GLFW fire both keyPressEvent() and textInputEvent() for each key that can be treated as text input. I was digging in SDL2 sources to find out a way if this behavior can be configured, but it just unconditionally fires both. Looking at GLFW docs, there's no way to override this either (didn't check the source tho) :/

If you scroll through the channel archives in the above link, an ImGui-specific workaround involves checking ImGui::GetIO().wantCaptureMouse and ImGui::GetIO().wantTextInput in addition to the return value from handleKeyPressEvent(), so maybe that could be a (temporary) solution for you as well?

A proper fix needs to be done on the Sdl2Application / GlfwApplication side, but so far I'm pretty clueless as how the fix should look, especially since the key press is fired before the text input, which is exactly the other way than what would be ~easily fixable. Googling around, I only found this thread but it quickly turned into a heated discussion involving OOP, with no useful information whatsoever.

from magnum-integration.

So

if (m_imgui.handleKeyPressEvent(event) || ImGui::GetIO().WantTextInput)
    return;

seems to be working fine, thanks for the quick suggestion! I've left out the ImGui::GetIO().WantCaptureMouse, since the even hovering a DragFloat would eat but the events.

Is there any reason this solution is just a temporary fix? Otherwise this could just be done automatically by handleKeyPressEvent.

from magnum-integration.

If I'm not mistaken, the above is doing the same as this:

if (m_imgui.handleKeyPressEvent(event) || isTextInputActive())
    return;

This in practice means, if any text input widget is active, it disallows handling of any key press events. For example, that would mean Ctrl S to trigger a file save would not be working if a text area is focused. Or F1 to open a help. Etc.

So while the above works for you (and for majority of other users as well), the proper fix is to suppress the key press event only if it really produces some text input. And that's a thing I currently don't know how to handle portably -- it needs to take into account dead keys (diacritics), Unicode, IME etc.

from magnum-integration.

Good to know, thanks for the explanation!

from magnum-integration.