mirror of
https://github.com/godotengine/godot-docs.git
synced 2026-01-05 22:09:56 +03:00
Fix typos using codespell
Running `find -name "*.rst" -exec codespell -w {} \;`.
This commit is contained in:
@@ -69,7 +69,7 @@ precise enough to be worked on.
|
|||||||
|
|
||||||
**Topics:**
|
**Topics:**
|
||||||
|
|
||||||
- *Assetlib*: relates to issues whith the asset library.
|
- *Assetlib*: relates to issues with the asset library.
|
||||||
- *Buildsystem*: relates to building issues, either linked to the SCons
|
- *Buildsystem*: relates to building issues, either linked to the SCons
|
||||||
buildsystem or to compiler peculiarities.
|
buildsystem or to compiler peculiarities.
|
||||||
- *Core*: anything related to the core engine. It might be further
|
- *Core*: anything related to the core engine. It might be further
|
||||||
|
|||||||
@@ -56,7 +56,7 @@ there to achieve our goal.
|
|||||||
For our goal (tip of the bone moved within area of target), we need to know
|
For our goal (tip of the bone moved within area of target), we need to know
|
||||||
where the tip of our IK bone is. As we don't use a leaf bone as IK bone, we
|
where the tip of our IK bone is. As we don't use a leaf bone as IK bone, we
|
||||||
know the coordinate of the bone base is the tip of parent bone. All these
|
know the coordinate of the bone base is the tip of parent bone. All these
|
||||||
calculations are quite dependant on the skeleton's structure. You can use
|
calculations are quite dependent on the skeleton's structure. You can use
|
||||||
pre-calculated constants as well. You can add an extra bone for the tip of
|
pre-calculated constants as well. You can add an extra bone for the tip of
|
||||||
IK and calculate using that.
|
IK and calculate using that.
|
||||||
|
|
||||||
|
|||||||
@@ -43,7 +43,7 @@ Setting up Pywin32
|
|||||||
|
|
||||||
Pywin32 is required for -j (parallel) builds for multiple cores (for a
|
Pywin32 is required for -j (parallel) builds for multiple cores (for a
|
||||||
32 bit Python version). If SCons is issuing a warning about Pywin32
|
32 bit Python version). If SCons is issuing a warning about Pywin32
|
||||||
after parsing SConstruct build instructions, when begining to build,
|
after parsing SConstruct build instructions, when beginning to build,
|
||||||
you need to install it properly from the correct installer executable
|
you need to install it properly from the correct installer executable
|
||||||
for your python version `located at Sourceforge. <https://sourceforge.net/projects/pywin32/files/pywin32/>`__
|
for your python version `located at Sourceforge. <https://sourceforge.net/projects/pywin32/files/pywin32/>`__
|
||||||
|
|
||||||
|
|||||||
@@ -70,7 +70,7 @@ Terminating the networking feature:
|
|||||||
Managing connections
|
Managing connections
|
||||||
--------------------
|
--------------------
|
||||||
|
|
||||||
Some games accept conections at any time, others during the lobby phase. Godot can be requested to no longer accept
|
Some games accept connections at any time, others during the lobby phase. Godot can be requested to no longer accept
|
||||||
connections at any point. To manage who connects, Godot provides the following signals in SceneTree:
|
connections at any point. To manage who connects, Godot provides the following signals in SceneTree:
|
||||||
|
|
||||||
Server and Clients:
|
Server and Clients:
|
||||||
|
|||||||
@@ -774,7 +774,7 @@ There are 6 pattern types:
|
|||||||
|
|
||||||
**Open-ended array**: An array can be bigger than the pattern by making the last subpattern ``..``
|
**Open-ended array**: An array can be bigger than the pattern by making the last subpattern ``..``
|
||||||
|
|
||||||
Every subpattern has to be comma seperated. ::
|
Every subpattern has to be comma separated. ::
|
||||||
|
|
||||||
match x:
|
match x:
|
||||||
[]:
|
[]:
|
||||||
@@ -793,11 +793,11 @@ There are 6 pattern types:
|
|||||||
|
|
||||||
**Open-ended dictionary**: A dictionary can be bigger than the pattern by making the last subpattern ``..``
|
**Open-ended dictionary**: A dictionary can be bigger than the pattern by making the last subpattern ``..``
|
||||||
|
|
||||||
Every subpattern has to be comma seperated.
|
Every subpattern has to be comma separated.
|
||||||
|
|
||||||
If you don't specify a value, then only the existance of the key is checked.
|
If you don't specify a value, then only the existence of the key is checked.
|
||||||
|
|
||||||
A value pattern is seperated from the key pattern with a ``:`` ::
|
A value pattern is separated from the key pattern with a ``:`` ::
|
||||||
|
|
||||||
match x:
|
match x:
|
||||||
{}:
|
{}:
|
||||||
@@ -812,7 +812,7 @@ There are 6 pattern types:
|
|||||||
print("I only checked for one entry and ignored the rest")
|
print("I only checked for one entry and ignored the rest")
|
||||||
|
|
||||||
Multipatterns:
|
Multipatterns:
|
||||||
You can also specify multiple patterns seperated by a comma. These patterns aren't allowed to have any bindings in them. ::
|
You can also specify multiple patterns separated by a comma. These patterns aren't allowed to have any bindings in them. ::
|
||||||
|
|
||||||
match x:
|
match x:
|
||||||
1, 2, 3:
|
1, 2, 3:
|
||||||
|
|||||||
@@ -117,7 +117,7 @@ As you know, the ``_ready()`` function is the first function called
|
|||||||
(after ``_enter_tree()`` which we don't need here). In this function,
|
(after ``_enter_tree()`` which we don't need here). In this function,
|
||||||
two things have to be done. The first one is to enable
|
two things have to be done. The first one is to enable
|
||||||
processing: this is the purpose of the ``set_process(true)`` function.
|
processing: this is the purpose of the ``set_process(true)`` function.
|
||||||
The second one is to initalize our two member variables.
|
The second one is to initialize our two member variables.
|
||||||
|
|
||||||
::
|
::
|
||||||
|
|
||||||
@@ -187,7 +187,7 @@ integrating it is simple:
|
|||||||
|
|
||||||
::
|
::
|
||||||
|
|
||||||
# Integrate new ball postion
|
# Integrate new ball position
|
||||||
ball_pos += direction * ball_speed * delta
|
ball_pos += direction * ball_speed * delta
|
||||||
|
|
||||||
This code line is called at each iteration of the ``_process()``
|
This code line is called at each iteration of the ``_process()``
|
||||||
|
|||||||
Reference in New Issue
Block a user