diff options
| author | weerdy15 <77104725+ItsAleph@users.noreply.github.com> | 2023-01-08 15:15:53 +0300 |
|---|---|---|
| committer | Rémi Verschelde <rverschelde@gmail.com> | 2023-01-10 18:21:03 +0100 |
| commit | 5aadb1273b1bd9e031fb0ad972a9ea9371fc8a3f (patch) | |
| tree | 61e38d7ffb940a1a0ff7cda93caf91743cbf54cc | |
| parent | 91713ced81792b10fdc9367b7f355738e5d52777 (diff) | |
docs: Improve `InputEventAction` reference
Co-authored-by: Rémi Verschelde <rverschelde@gmail.com>
| -rw-r--r-- | doc/classes/InputEventAction.xml | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/classes/InputEventAction.xml b/doc/classes/InputEventAction.xml index 87e2b8ea20..3816847804 100644 --- a/doc/classes/InputEventAction.xml +++ b/doc/classes/InputEventAction.xml @@ -5,6 +5,7 @@ </brief_description> <description> Contains a generic action which can be targeted from several types of inputs. Actions can be created from the [b]Input Map[/b] tab in the [b]Project > Project Settings[/b] menu. See [method Node._input]. + [b]Note:[/b] Unlike the other [InputEvent] subclasses which map to unique physical events, this virtual one is not emitted by the engine. This class is useful to emit actions manually with [method Input.parse_input_event], which are then received in [method Node._input]. To check if a physical event matches an action from the Input Map, use [method InputEvent.is_action] and [method InputEvent.is_action_pressed]. </description> <tutorials> <link title="InputEvent: Actions">$DOCS_URL/tutorials/inputs/inputevent.html#actions</link> |