From 9688a6eaf05e7dc20a74903900dfc6a7507ec043 Mon Sep 17 00:00:00 2001 From: reduz Date: Sun, 2 Nov 2014 19:10:22 -0800 Subject: [PATCH] Updated tutorial_input_events (markdown) --- tutorial_input_events.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/tutorial_input_events.md b/tutorial_input_events.md index a769897..86571bc 100644 --- a/tutorial_input_events.md +++ b/tutorial_input_events.md @@ -72,7 +72,5 @@ get_tree().input_event(ev) ``` ### InputMap -Customizing and re-mapping input from code is often desired. If your whole workflow depends on actions, the [InputMap](class_inputmap) singleton is ideal for reassigning or creating different actions at run-time. +Customizing and re-mapping input from code is often desired. If your whole workflow depends on actions, the [InputMap](class_inputmap) singleton is ideal for reassigning or creating different actions at run-time. This singleton is not saved (must be modified manually) and it's state is run from the project settings (engine.cfg). So any dynamic system of this type needs to store settings in the way the programmer sees best fit. - --explain InputMap and how to map to user-events. \ No newline at end of file