mirror of
https://github.com/stan220/godot-docs.git
synced 2026-09-08 18:29:11 +00:00
Draft: Remove "simple", "simply", "easy", and "just" from the docs (#4496)
* Various style edits * Edit out "simple" when possible Co-authored-by: Max Hilbrunner <mhilbrunner@users.noreply.github.com> Co-authored-by: Clay John <claynjohn@gmail.com>
This commit is contained in:
co-authored by
Max Hilbrunner
Clay John
parent
a4a368af15
commit
bd19917ea0
@@ -17,7 +17,7 @@ Godot supports threads and provides many handy functions to use them.
|
||||
Creating a Thread
|
||||
-----------------
|
||||
|
||||
Creating a thread is very simple, just use the following code:
|
||||
To create a thread, use the following code:
|
||||
|
||||
.. tabs::
|
||||
.. code-tab:: gdscript GDScript
|
||||
|
||||
@@ -9,9 +9,9 @@ resources simplifies project organization and asset management in complex games.
|
||||
|
||||
There are, of course, always drawbacks:
|
||||
|
||||
* There is an extra layer of complexity
|
||||
* Performance is lower than using simple APIs directly
|
||||
* It is not possible to use multiple threads to control them
|
||||
* There is an extra layer of complexity.
|
||||
* Performance is lower than when using simple APIs directly.
|
||||
* It is not possible to use multiple threads to control them.
|
||||
* More memory is needed.
|
||||
|
||||
In many cases, this is not really a problem (Godot is very optimized, and most operations are handled
|
||||
@@ -83,7 +83,7 @@ functions should always be used for creating and controlling new ones and intera
|
||||
Creating a sprite
|
||||
-----------------
|
||||
|
||||
This is a simple example of how to create a sprite from code and move it using the low-level
|
||||
This is an example of how to create a sprite from code and move it using the low-level
|
||||
:ref:`CanvasItem <class_CanvasItem>` API.
|
||||
|
||||
.. tabs::
|
||||
|
||||
Reference in New Issue
Block a user