Fix the Node process_priority
description to match actual behavior
This closes #34531.
This commit is contained in:
parent
ac046b7bac
commit
0bab51ab55
1 changed files with 1 additions and 1 deletions
|
@ -839,7 +839,7 @@
|
||||||
Pause mode. How the node will behave if the [SceneTree] is paused.
|
Pause mode. How the node will behave if the [SceneTree] is paused.
|
||||||
</member>
|
</member>
|
||||||
<member name="process_priority" type="int" setter="set_process_priority" getter="get_process_priority" default="0">
|
<member name="process_priority" type="int" setter="set_process_priority" getter="get_process_priority" default="0">
|
||||||
The node's priority in the execution order of the enabled processing callbacks (i.e. [constant NOTIFICATION_PROCESS], [constant NOTIFICATION_PHYSICS_PROCESS] and their internal counterparts). Nodes with a higher process priority will have their processing callbacks executed first.
|
The node's priority in the execution order of the enabled processing callbacks (i.e. [constant NOTIFICATION_PROCESS], [constant NOTIFICATION_PHYSICS_PROCESS] and their internal counterparts). Nodes whose process priority value is [i]lower[/i] will have their processing callbacks executed first.
|
||||||
</member>
|
</member>
|
||||||
</members>
|
</members>
|
||||||
<signals>
|
<signals>
|
||||||
|
|
Loading…
Reference in a new issue