You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm currently implementing a scripted imgui environment, using DearGui python bindings.
It's a fairly common mistake to omit the ::End() call, and thus get an assertion about it.
I was wondering if this will yield me any wierd behaviour or obscure bugs:
ImGuiContext* g = ImGui::GetCurrentContext();
while (g->CurrentWindowStack.Size > 1)
{
printWarning("ImGui window missing ::End()!\n");
ImGui::End();
}
This would spit tons of warnings, but at least not crash the application, which would be detrimental in my use case.
I've of course tried it out, and it seems to work fine, but I'm left wondering if it's a dirty hack or actually an OK way of doing it.
Are there any other ways of making ImGui less "strict" with assertions?
I'm aware that there are other places where missing a corresponding End call might assert as well, but I'll worry about those later.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi,
I'm currently implementing a scripted imgui environment, using DearGui python bindings.
It's a fairly common mistake to omit the ::End() call, and thus get an assertion about it.
I was wondering if this will yield me any wierd behaviour or obscure bugs:
This would spit tons of warnings, but at least not crash the application, which would be detrimental in my use case.
I've of course tried it out, and it seems to work fine, but I'm left wondering if it's a dirty hack or actually an OK way of doing it.
Are there any other ways of making ImGui less "strict" with assertions?
I'm aware that there are other places where missing a corresponding End call might assert as well, but I'll worry about those later.
Thanks!
The text was updated successfully, but these errors were encountered: