Fix mixed use of tabs and spaces in indented blocks

4-space is our convention for indented blocks and should be used consistently.
The only exception is for C++ code which is tab-indented, as the engine code.
This commit is contained in:
Rémi Verschelde
2018-11-20 11:02:11 +01:00
parent 6274c53536
commit a0e32ac017
31 changed files with 477 additions and 489 deletions

View File

@@ -171,8 +171,7 @@ Return whether the custom node has an input **sequence** port.
Execute the custom node's logic, returning the index of the output sequence port to use or a :ref:`String<class_String>` when there is an error.
The ``inputs`` array contains the values of the input ports.
The ``inputs`` array contains the values of the input ports.
``outputs`` is an array whose indices should be set to the respective outputs.
@@ -180,6 +179,5 @@ The ``start_mode`` is usually ``START_MODE_BEGIN_SEQUENCE``, unless you have use
``working_mem`` is an array which can be used to persist information between runs of the custom node.
When returning, you can mask the returned value with one of the STEP\_\* constants.
When returning, you can mask the returned value with one of the STEP\_\* constants.