stan220/godot-docs
1
0
Fork 0
mirror of https://github.com/stan220/godot-docs.git synced 2026-09-08 18:29:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Link to Getting Started Input tutorial from Input examples page (#10200)

Browse Source 
* Link to Getting Started Input tutorial from Input examples page

---------

Co-authored-by: Hugo Locurcio <hugo.locurcio@hugo.pro>
This commit is contained in:
tetrapod
2024-11-05 00:38:49 +01:00
committed by GitHub
co-authored by Hugo Locurcio
parent c77b4d1905
commit f0b5879b85
2 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
getting_started/first_3d_game/02.player_input.rst
+2
View File
@@ -84,6 +84,8 @@ Save the scene as ``player.tscn``
With the nodes ready, we can almost get coding. But first, we need to define With the nodes ready, we can almost get coding. But first, we need to define
some input actions. some input actions.
.. _doc_first_3d_game_input_actions:
Creating input actions Creating input actions
---------------------- ----------------------
tutorials/inputs/inputevent.rst
+9 -3
View File
@@ -194,10 +194,10 @@ There are several specialized types of InputEvent, described in the table below:
| | as feedback. (more on this below) | | | as feedback. (more on this below) |
+-------------------------------------------------------------------+-----------------------------------------+ +-------------------------------------------------------------------+-----------------------------------------+
Actions Input actions
------- -------------
Actions are a grouping of zero or more InputEvents into a commonly Input actions are a grouping of zero or more InputEvents into a commonly
understood title (for example, the default "ui_left" action grouping both joypad-left input and a keyboard's left arrow key). They are not required to represent an understood title (for example, the default "ui_left" action grouping both joypad-left input and a keyboard's left arrow key). They are not required to represent an
InputEvent but are useful because they abstract various inputs when InputEvent but are useful because they abstract various inputs when
programming the game logic. programming the game logic.
@@ -239,6 +239,12 @@ The Input singleton has a method for this:
// Feedback. // Feedback.
Input.ParseInputEvent(ev); Input.ParseInputEvent(ev);
.. seealso::
See :ref:`doc_first_3d_game_input_actions` for a tutorial on adding input
actions in the project settings.
InputMap InputMap
-------- --------