feature request: add support for tracking signals connected through code

[NickMakesGames]

This plugin works great for projects that have complex signal trees defined through the scene editor. However, a common pattern for Godot is to use a "Signal Bus," which defines signals in a global autoload. Individual components can then subscribe to those signals through code.

I imagine it would be very helpful to have an option to generate a graph based on a file, which displays all the places in code where that file's signals are connected to, as well as the places in code that emit that file's signals. Is something like this possible with the way your visualizer is implemented?

[Ericdowney]

@NickMakesGames Hey! The latest release, 1.7.0, should have this capability. It's located under the Debugger Panel, then Signal Debugger tab. However, I don't believe I tested this functionality with signals configured through an Autoload. If it doesn't work, let me know and I can make a fix.

[NickMakesGames]

hm, trying my game in the Godot 4.3 beta 1, it doesn't seem to work. My repro steps are:

• Launch Engine
• Press the "play" button to run the game
• tab over to the Godot editor >debugger > signal debugger
• click "start"
• tab over to the running game
• perform some action in game that emits a global signal
• tab back over to the Godot editor

Expected: The emitted signal should appear in the debugger Actual: The entire editor freezes and needs to be force quit.

I'll try to find some time to repro this on a Godot 4.2 (and maybe try it on a simple test project instead of an already late-in-development game) and let you know what happens.