Key Events have changed in ImGui

[mosra]

Key Events have changed in ImGui

[pezcode]

I opened a PR that should at least fix the backward compatibility. Let me know if that works for you or doesn't (ideally on the PR page).

[mosra]

This is now fixed with #93, merged as c60149c.

[pezcode]

I'm gonna leave this here, some useful info on the why's and how's: ocornut/imgui#4858. Also note this little comment from the same link:

I think we will try to make some more use of it before declaring the change valid.

Might be worth waiting until this hits a tagged release to actually add support for this, in case they pull or rework this.

[jvannugteren]

Fair enough. The "backwards compatibility" doesn't currently work for us though.

[pezcode]

Okay, I understand the immediate issue now. Regardless of the AddKeyEvent changes, we should have been doing something like:

// at startup
io.KeyMap[ImGuiKey_Tab] = KeyEvent::Key::Tab;

// in the switch
io.KeysDown[KeyEvent::Key::Tab];

This fixes the issue of out-of-bounds indexing io.KeysDown with the new remapped ImGuiKey enum, and as a nice side-effect we can save ourselves the switch altogether + users get a full key map in io.KeysDown with platform-specific keys.

The AddKeyEvent changes need a bit more thought, since we need backwards-compatibility with older imgui versions.

[pezcode]

Actually it's not as simple: ocornut/imgui#2269 (comment)

Maybe for now we have to hack around this by ifdefing around ImGuiKey_Tab being >= 512 and then subtracting ImGuiKey_NamedKey_BEGIN. Sigh 😵‍

[ocornut]

Indeed this is one (unusual but technically valid) use case we didn't think about when designing the backward compatibility....
Unfortunately I'm not sure how we can fix it.
We will be adding new asserts to detect it + mark this specific use case as a breaking change.

[ocornut]

Might be worth waiting until this hits a tagged release to actually add support for this, in case they pull or rework this.

FYI the Key aspect of this change IHMO at this point is a settled API.
Bug/tweaks may arise before we tag 1.87 but your feedback here would be super helpful.

What will not yet committed and will come before we tag 1.87 is transitioning other inputs into event calls (e.g io.AddMouseButtonEvent() standardizing the new IO API and allowing trickling input queue (to handle very slow framerate better). That may be pushed next week.

[jvannugteren]

Sure I'll keep an eye out for issues that may emerge due to these changes. My "Rat" GUI code requires docking branch, so normally I find out when you merge the master into that.

[jvannugteren]

Many thanks. (=