gaming/godot
gaming/godot
1
0
Fork 0
mirror of https://github.com/godotengine/godot synced 2024-07-05 16:03:36 +00:00
Code Issues Projects Releases Wiki Activity

Updated tutorial_input_events (markdown)

reduz 2014-11-02 18:33:09 -08:00
parent 15cda39290
commit a0b98b59c3
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
tutorial_input_events.md

@ -20,7 +20,26 @@ But SceneTree does not know what to do with the event, so it will give it to the
### Anatomy of an InputEvent
[InputEvent](class_inputevent) is just a base built-in type, it does not represent anything and only contains some basic information, such as event ID (which is increased for each event), device index, etc.
InputEvent has a "type" member. By assigning it, it can become different types of input event. Every type of InputEvent has different properties, according to it's role.
Example of changing event type.
```python
# create event
var ev = InputEvent.new()
# set type
ev.type=InputEvent.MOUSE_BUTTON
# button_index is only available for the above type
ev.button_index=BUTTON_LEFT
```
There are several types of InputEvent, described in the table below:
| Event | Type Index | Description |
|-------|------------|-------------|
|[InputEvent](class_inputevent)|NONE|Empty Input Event|
|[InputEventKey](class_inputeventkey)|KEY|Contains a scancode and unicode value, as well as modifiers|