Open mieldepoche opened 11 months ago
This feels overly specific. Are there really going to be so many "possibly broken" nodes, even in a large scene tree? Clicking on "unfold all" and scrolling down sounds... reasonable enough for me.
OP clearly names "configuration warnings" in the title, so "possibly broken" nodes refers to those that have warnings (yellow triangles) on them
I am aware of that.
I'd prefer a solution like https://github.com/godotengine/godot-proposals/issues/5068 as it could work globally, rather than being scoped to a specific scene (although you could choose the auditing tool to be scoped to a scene).
Describe the project you are working on
prototype
Describe the problem or limitation you are having in your project
related to #8251 There's no easy way to find nodes that have configuration warnings.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
You can filter nodes by name, type or group in the scene dock. Add a way to filter them by configuration warning status.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
letter:thing
syntax, but it's hard to find something good for that kind of thing. Maybew:yes
(as opposed tow:no
which would then be expected to filter warned nodes out of the selection though that's useless?)?⋮ > Filters
menu of the scene dock.If this enhancement will not be used often, can it be worked around with a few lines of script?
it's an editor feature that would be used a bit
Is there a reason why this should be core and not an add-on in the asset library?
I don't know if this can be an addon