[fisica638]

EasyImGui allows you to Create your GUI with ImGui, without having to configure anything, you don't need any additional knowledge.
You just need to install EasyImGui from NuGet and that's it! .
EasyImGui has two Imgui Views:

1. ImGuiForm: A Single View, It does not support multi-Windows, and to work, it must be Launched with: 
   
   Code

   Application.Run(SingleImguiWindow);
    .
   
2. MultiImGuiForm: Allows Multiple Imgui Windows, It can be launched normally with 
   
   Code

   .Show()
   , It has no restrictions and using WinAPIS, you could embed the windows in Controls Panel or in other Forms.
   

Note:
If within your ImGui code you launch controls that block the Main UI, such as OpenFileDialog or MessageBox.Show, it will cause your application to fail, this is easy to solve, Simply do everything Asynchronously, Without Dialogs.

Github : https://github.com/DestroyerDarkNess/EasyImGui

Preview

[Klonopin]

Cool, I don't see the C++ version much harder, but neat to see it working on Csharp.
much rather stick with C++ imgui though.

[HFDone]

saw thread with reply about it c++ look very nice
good job for your c# version
Edit - saw that you used DearImguiSharp warpper any way well done

[Suspect.]

Looks decent, code could be improved by handling your exceptions better but still a good release.

[fisica638]

saw thread with reply about it c++ look very nice
good job for your c# version
Edit - saw that you used DearImguiSharp warpper any way well done

Imgui.NET, if you are not using modern C#, properties and methods appear as private/read-only; In languages like VB.NET, all properties also appear as read-only.

On the other hand, DearImguiSharp, despite some small problems, can be fixed with additional code. The downside would be that it is outdated.

In any case, I'm considering creating a separate branch of the project, which uses Imgui.NET, but only as a test branch.

The idea of EasyImgui is to be as stable as possible with C# and VB.NET, and of course with the .net framework.

Actually, I don't know why I wrote this either, since "ClickableTransparentOverlay" exists.

EasyImgui would be an alternative to ClickableTransparentOverlay, but much more outdated. since EasyImgui uses Dx9 + .Net Framework + DearImguiSharp (an obsolete imgui wrapper)

Looks decent, code could be improved by handling your exceptions better but still a good release.

Yes, in fact the bugs I found, I corrected during production. I had to upload several versions to nuget, and each of those versions corrected some bug.

Although the latest version is the most stable. I didn't find any more errors.

about exception handling... I was lazy XD, as was commenting on the code.

Well actually I thought I didn't need it, since any errors when creating the device and during rendering will be handled by SharpDX. and displayed as a message. everything else that could fail would be the hook to implement Imgui.

[Klonopin]

Imgui.NET, if you are not using modern C#, properties and methods appear as private/read-only; In languages like VB.NET, all properties also appear as read-only.

On the other hand, DearImguiSharp, despite some small problems, can be fixed with additional code. The downside would be that it is outdated.

In any case, I'm considering creating a separate branch of the project, which uses Imgui.NET, but only as a test branch.

The idea of EasyImgui is to be as stable as possible with C# and VB.NET, and of course with the .net framework.

Actually, I don't know why I wrote this either, since "ClickableTransparentOverlay" exists.

EasyImgui would be an alternative to ClickableTransparentOverlay, but much more outdated. since EasyImgui uses Dx9 + .Net Framework + DearImguiSharp (an obsolete imgui wrapper)


Yes, in fact the bugs I found, I corrected during production. I had to upload several versions to nuget, and each of those versions corrected some bug.

Although the latest version is the most stable. I didn't find any more errors.

about exception handling... I was lazy XD, as was commenting on the code.

Well actually I thought I didn't need it, since any errors when creating the device and during rendering will be handled by SharpDX. and displayed as a message. everything else that could fail would be the hook to implement Imgui.

Why not just use C++ imgui and directx11 for your application?

[fisica638]

Why not just use C++ imgui and directx11 for your application?

Doing this in c++ is very easy, everyone does it in c++. The idea of this Project is to be able to do everything in .NET, with C# or VB.NET, that is the real challenge.

[Klonopin]

Doing this in c++ is very easy, everyone does it in c++. The idea of this Project is to be able to do everything in .NET, with C# or VB.NET, that is the real challenge.

Hm, sure. if you're just doing it for fun I guess. but there's no point when you've got Winforms & WPF if you're actually trying to build a project.

WinForms and WPF are as customizable as Imgui.

[fisica638]

If you see it that way, you're right. But remember that this is an addition, not a replacement to Winform/WPF.

You see this, as an obsession of mine, that I always wanted to use imgui, but it had limitations, since my knowledge only covered VB.NET and .NET Framework. now after learning C# I finally managed to do it.