Closed jvannugteren closed 2 years ago
I have a patch for this, just stashed it because there was some other work I originally wanted to do on ImGuiIntegration. I can send a PR tomorrow ☺️
Thanks. Did you happen to also fix the key events? Then I won't need to make another issue.
Thanks. Did you happen to also fix the key events? Then I won't need to make another issue.
Hm no, not aware of key event issues. Feel free to file an issue.
Thanks! The code here originates way before 1.71 was a thing and since I'm not using ImGui myself, I'm not really reading the changelogs and so I missed this, sorry -- glad you've discovered the issue instead.
Using the magnum-integration I get the following graphical glitch with ImGui: https://github.com/ocornut/imgui/releases/tag/v1.86 (see first section)
I have created an issue there. However, I was pointed out by Ocornut, creator of imgui, it is an issue with the backend (i.e. Magnum) not honoring the ImDrawCmd::IdxOffset correctly.
See the following ImGui issues (all the same): https://github.com/ocornut/imgui/issues/4887 (this one is mine) https://github.com/ocornut/imgui/issues/4863 https://github.com/ocornut/imgui/issues/4845
I think the (easy) fix is to change src/Magnum/ImGuiIntegration/Context.cpp line 328 to:
Lines 310 and 333 then become obsolete. This way the IdxOffset of ImGui is respected and not re-calculated by magnum. With this change the glitch goes away at least in my code. Please check what I did as I'm not fully familiar with your code.
Thanks for looking at this.