Node Signals Not Listed in the API Reference?

Geebee

Good afternoon!

I've sat down and started trying to wrap my head around how Godot works, and was working through the tutorial on signals (https://docs.godotengine.org/en/stable/getting_started/step_by_step/signals.html). I learned how every node has a set of signals they can emit. To make sure I know what signals are available, I started reading through the docs for the different built-in nodes.

EDIT: The question was supposed to be "are the node signals listed in the API reference, and why can't I find them?" Somehow this didn't end up in the final post...I later found out that, to find signals for a node that inherits from another node, you have to look at the reference in it's parent node (e.g. because KineticBody2D inherits some signals from Node2D, those signals are listed in the reference for Node2D and not in KineticBody2D). I appreciate the clarifications!

Megalomaniak

Is there a question? Note that also custom signals can be created so if you see someone use a signal that documentation doesn't cover it might be a custom one.

TwistedTwigleg

Something to add: Each node in the Godot documentation shows the built-in signals that each node exposes, including which variables/arguments it passes. You can also see the built-in signals of a node by selecting the node in the Godot editor and pressing the signals tab in the inspector, or at least I think that's what it's called. Its a tab on the right side of the inspector, I know that much, and it shows the signals and the name of the variables/arguments passed.

Geebee

@TwistedTwigleg said: You can also see the built-in signals of a node by selecting the node in the Godot editor and pressing the signals tab in the inspector, or at least I think that's what it's called.

Right, this is what threw me for a loop at first. In KinematicBody2D, the Signals pane listed several signals available, yet the KinematicBody2D documentation never mentioned them. Then on closer inspection, it was because the listed signals were from other classes related to it (e.g. CollisionObject2D, CanvasItem, etc), which did have documentation on their signals. Once I saw the signals were listed there didn't directly come from the node in question it started to make sense. Thanks for the help!