Clarify get_indexed in relation to Nodes

(cherry picked from commit 4ea6709558)
This commit is contained in:
kobewi 2021-11-22 01:26:55 +01:00 committed by Rémi Verschelde
parent 4876686cf7
commit b8bda1fb67
No known key found for this signature in database
GPG key ID: C3336907360768E1

View file

@ -201,6 +201,7 @@
<argument index="0" name="property" type="NodePath" /> <argument index="0" name="property" type="NodePath" />
<description> <description>
Gets the object's property indexed by the given [NodePath]. The node path should be relative to the current object and can use the colon character ([code]:[/code]) to access nested properties. Examples: [code]"position:x"[/code] or [code]"material:next_pass:blend_mode"[/code]. Gets the object's property indexed by the given [NodePath]. The node path should be relative to the current object and can use the colon character ([code]:[/code]) to access nested properties. Examples: [code]"position:x"[/code] or [code]"material:next_pass:blend_mode"[/code].
[b]Note:[/b] Even though the method takes [NodePath] argument, it doesn't support actual paths to [Node]s in the scene tree, only colon-separated sub-property paths. For the purpose of nodes, use [method Node.get_node_and_resource] instead.
</description> </description>
</method> </method>
<method name="get_instance_id" qualifiers="const"> <method name="get_instance_id" qualifiers="const">