Usage with Hexa.NET.ImGui

[Aman-Anas]

Hi, I'm using C# (only) and I was wondering if it's possible to use Hexa.NET.ImGui rather than the Imgui.NET package. This is because ImGui.NET is missing the "Internal" methods of Dear Imgui. These are very useful for things like setting up docking layouts and custom drawing functionality. More info here: ImGuiNET/ImGui.NET#81

Anyways, Hexa.NET.ImGui seems to be much more up-to-date, and it seems to be easier to do the native interop as well. I'm working through updating the ImGuiGodot internal files to switch over in my project and it's almost a drop-in replacement except for cleaning up the pointers and native stuff.

EDIT: it looks like @maidopi-usagi already made an integration already, mentioned here: #75 (comment) . I am having some trouble getting it to run though.

[pkdawson]

Thanks for letting me know about Hexa.NET.ImGui. It's not practical to support both due to numerous small API differences, but if it's going to be more actively maintained than ImGui.NET, I will definitely explore switching to it in the near future.

[mrawlingst]

Second. Hexa is miles ahead, and it's surprising how far behind ImGui.NET has fallen in comparison. I've often found myself needing access to ImGui internals as well. Currently, I'm trying to update this to the latest version and get it working with Hexa, but haven’t had much luck so far.

Edit: I legit just remembered to check if there's branches for Hexa. Lo and behold, I see a hexa branch.

[pkdawson]

Yeah with ImGui.NET still not updated, I'm ready to make the switch. I've got the port to Hexa.NET working, just a few small things to do before releasing 7.0.0.

[mrawlingst]

Yeah, I've switched to that branch and it worked flawlessly with some tweaks to my code due to API changes. So far I haven't run into any issues yet. I'll let you know if I do.