Specify order of drawing of Nodes in raise() description
(cherry picked from commit a67ef5999d
)
This commit is contained in:
parent
0239337475
commit
d2241a2b5f
1 changed files with 1 additions and 1 deletions
|
@ -570,7 +570,7 @@
|
|||
<return type="void">
|
||||
</return>
|
||||
<description>
|
||||
Moves this node to the bottom of parent node's children hierarchy. This is often useful in GUIs ([Control] nodes), because their order of drawing depends on their order in the tree, i.e. the further they are on the node list, the higher they are drawn. After using [code]raise[/code], a Control will be drawn on top of their siblings.
|
||||
Moves this node to the bottom of parent node's children hierarchy. This is often useful in GUIs ([Control] nodes), because their order of drawing depends on their order in the tree. The top Node is drawn first, then any siblings below the top Node in the hierarchy are successively drawn on top of it. After using [code]raise[/code], a Control will be drawn on top of its siblings.
|
||||
</description>
|
||||
</method>
|
||||
<method name="remove_and_skip">
|
||||
|
|
Loading…
Reference in a new issue