From 3d34a259173ded09a4ec7d8de345516550d12df4 Mon Sep 17 00:00:00 2001 From: Hendrik Brucker Date: Sat, 29 Jun 2024 19:39:34 +0200 Subject: [PATCH] [GraphEdit] Add a note about the behavior of get_children() --- doc/classes/GraphEdit.xml | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/classes/GraphEdit.xml b/doc/classes/GraphEdit.xml index 001839d74525..670df10a89cc 100644 --- a/doc/classes/GraphEdit.xml +++ b/doc/classes/GraphEdit.xml @@ -7,6 +7,7 @@ [GraphEdit] provides tools for creation, manipulation, and display of various graphs. Its main purpose in the engine is to power the visual programming systems, such as visual shaders, but it is also available for use in user projects. [GraphEdit] by itself is only an empty container, representing an infinite grid where [GraphNode]s can be placed. Each [GraphNode] represents a node in the graph, a single unit of data in the connected scheme. [GraphEdit], in turn, helps to control various interactions with nodes and between nodes. When the user attempts to connect, disconnect, or delete a [GraphNode], a signal is emitted in the [GraphEdit], but no action is taken by default. It is the responsibility of the programmer utilizing this control to implement the necessary logic to determine how each request should be handled. [b]Performance:[/b] It is greatly advised to enable low-processor usage mode (see [member OS.low_processor_usage_mode]) when using GraphEdits. + [b]Note:[/b] Keep in mind that [method Node.get_children] will also return the connection layer node named [code]_connection_layer[/code] due to technical limitations. This behavior may change in future releases.