diff options
author | Rémi Verschelde <rverschelde@gmail.com> | 2023-01-11 09:48:47 +0100 |
---|---|---|
committer | Rémi Verschelde <rverschelde@gmail.com> | 2023-01-11 09:48:47 +0100 |
commit | ff4d5e0a68b285086628f59c96a4298e943015d6 (patch) | |
tree | 4d04e768e86686d010de180afdddd0241ea82a62 /doc | |
parent | 9af4628bbeecbb3348b3a462da3efff342db153e (diff) | |
parent | 5aadb1273b1bd9e031fb0ad972a9ea9371fc8a3f (diff) |
Merge pull request #71060 from ItsAleph/docs/improve-iea
docs: Improve `InputEventAction` reference
Diffstat (limited to 'doc')
-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> |