Thank you very much for the nice work. I think that developer community of Dear ImGUI will benefit a lot from this project.

I made tiny modifications to the C++ part so that it can compile cleanly using MSVC 2019 and replaced the Makefile with CMake. Also added workflow/actions for Windows and macOS.

You now need to install glfw only if the target platform is Linux. Windows & macOS will automatically download GLFW during the build process and build a static version that can then be linked against. This means that no brew is needed or macOS. It also means that native Windows runtime from VS2019 can be utilized and there's no need for mingw or msys runtimes. The app works pretty nicely on Windows. I haven't tried it yet on macOS, but the workflow builds with a few warnings.

The Windows Workflow will now also create an MSI installer that users can install and use right away.

Hope this helps. :)

ImGui::End() should always be called, even if ImGui::Begin() returns false. Otherwise ImGui will assert on a begin/end stack mismatch.

This might seem confusing initially, because ImGui widgets that have Begin/End calls should have their End calls inside the if block. However, that rule does not apply to ImGui windows.

Hello,

Thanks a lot for your nice tool, and sharing your code. I'll study your tool, and try to help if I can. Waiting, I found some little changes like fix some warnings. The change are under MIT license, i.e. for the script.

Feel free to use it, or not, and to do whatever you want of this PR.

Thank you very much for the nice work. I think that developer community of Dear ImGUI will benefit a lot from this project.

I made tiny modifications to the C++ part so that it can compile cleanly using MSVC 2019 and replaced the Makefile with CMake. Also added workflow/actions for Windows and macOS.

You now need to install glfw only if the target platform is Linux. Windows & macOS will automatically download GLFW during the build process and build a static version that can then be linked against. This means that no brew is needed or macOS. It also means that native Windows runtime from VS2019 can be utilized and there's no need for mingw or msys runtimes. The app works pretty nicely on Windows. I haven't tried it yet on macOS, but the workflow builds with a few warnings.

Hope this helps. :)

I'm working on a serializer for ImStudio so that I can save and load GUI projects (using yaml-cpp).

Admittedly, I'm not super familiar with how ImStudio stores and looks up children/parents, or rather, how the object hierarchy works, at the moment.

I wrote something like this pseudo code:

    if (obj.parent)
        out << "ParentID" << obj.parent->id;
    else
        out << "ParentID" << 0;

I then tested this serialization with a few widgets (no nesting) in a window, and the objects' parent ID always serialize as: ParentID: 30198988 (This turns out to be 0x01CCCCCC, probably some kind of magic number.) I tried adding the line parent = nullptr; to BaseObject's constructor, but this doesn't seem to make a difference. And also, when I put in a break point and look at the object that is currently being serialized, the obj.parent doesn't appear to be valid memory.

I was hoping you might be able to see if you have similar results with your object.parent, or if it's just something I did.

Also, I did notice that in the Object constructor, it seems to set itself as the parent of itself, so I'm thinking I may be misunderstanding your data structure, and it isn't tree-like?