Version/Branch of Dear ImGui:
Version 1.89.2, Branch: docking
Back-ends:
glfw, rust bindings
Compiler, OS:
Irrelevant
Full config/build information:
No response
Details:
When one creates a widget with the same ID, these days imgui will very helpfully generate a big red tooltip informing the user about it. It even very helpfully puts borders around the elements. Lovely.
The downside is that it can be a bit hard to find. We have an application with tens of windows and probably the number of elements is into thousands. Many of these aren't frequently used and even fewer are clicked.
Is there a way for imgui to inform us about duplicate IDs in some way that doesn't involve us randomly stumbling upon it and getting a tooltip? It doesn't have to be amazing: highlighting the elements would be more than enough. At this point I'd even take an (optional) crash so that I could work backwards from the stack trace to find the location.
This way we could open all the windows in the application and have extra confidence that we don't have duplicates. Of course it's not fool-proof and dynamic elements can slip through, but it'd be a lot better than having to hover over everything.
Thank you!
Screenshots/Video:
No response
Minimal, Complete and Verifiable Example code:
No response
Version/Branch of Dear ImGui:
Version 1.89.2, Branch: docking
Back-ends:
glfw, rust bindings
Compiler, OS:
Irrelevant
Full config/build information:
No response
Details:
When one creates a widget with the same ID, these days imgui will very helpfully generate a big red tooltip informing the user about it. It even very helpfully puts borders around the elements. Lovely.
The downside is that it can be a bit hard to find. We have an application with tens of windows and probably the number of elements is into thousands. Many of these aren't frequently used and even fewer are clicked.
Is there a way for imgui to inform us about duplicate IDs in some way that doesn't involve us randomly stumbling upon it and getting a tooltip? It doesn't have to be amazing: highlighting the elements would be more than enough. At this point I'd even take an (optional) crash so that I could work backwards from the stack trace to find the location.
This way we could open all the windows in the application and have extra confidence that we don't have duplicates. Of course it's not fool-proof and dynamic elements can slip through, but it'd be a lot better than having to hover over everything.
Thank you!
Screenshots/Video:
No response
Minimal, Complete and Verifiable Example code:
No response