Replies: 1 comment 3 replies
-
You are preaching to the choir! There are several reasons we initially went with the API design but the most important one is we didn't realize how much more powerful the immediate mode API was at the time. I've been using Dear ImGui now daily for years and I see my error. This is one of the main reasons we are working on a DPG 2 which will be closer to the Dear ImGui API. Actually, it will almost be a 1 to 1 mapping. So stick around for that! |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The IMGUI code lives inside a loop that runs once per frame like this:
This is great because you don't have to worry about state synchronization stuff, because every frame you are calling
ImGUI::whatever
with current data.This is in contrast to DearPyGui, where you have some setup code and then an loop that runs once per frame:
The key thing that made ImGui so great is that you didn't have to worry about UI state, since the UI was kinda reconstructed every frame (from the developer's POV). Now that is not to knock Dear PyGUI, it is still miles better than all the other Python gui libraries. I am just wondering why you went with this style of API?
Beta Was this translation helpful? Give feedback.
All reactions