Differences

This shows you the differences between two versions of the page.

--- en:tutorials:remapping_inputs [2018/09/28 07:53 (7 years ago)] – external edit 127.0.0.1
+++ en:tutorials:input:remapping_inputs [2020/08/31 14:11 (5 years ago)] (current) – ↷ Links adapted because of a move operation 76.14.89.164
@@ Line 6: / Line 6: @@
 <WRAP center round info 90%>
-If you wish to simply use the existing built-in mappings for all controllers, [[en:tutorials:analog_joystick_gamepad_control|check this article first]]. If you wish to learn about additional standard mappings for all controllers, see [[en:tutorials:overriding_controller_mapping|Overriding a Controller mapping]].
+If you wish to simply use the existing built-in mappings for all controllers, [[en:tutorials:input:analog_joystick_gamepad_control|check this article first]]. If you wish to learn about additional standard mappings for all controllers, see [[en:tutorials:input:overriding_controller_mapping|Overriding a Controller mapping]].
 </WRAP>
@@ Line 106: / Line 106: @@
 <WRAP center round tip 90%>
-**Note:** when using ''orxInput_GetActiveBinding'', it only collects an input for the specific frame. A slow custom clock will miss values especially if they are fast inputs like mouse wheel clicks. Therefore, it is recommended that the **core clock** is used. See [[en:tutorials:testing_input_controls|here]] for an example.
+**Note:** when using ''orxInput_GetActiveBinding'', it only collects an input for the specific frame. A slow custom clock will miss values especially if they are fast inputs like mouse wheel clicks. Therefore, it is recommended that the **core clock** is used. See [[en:tutorials:input:testing_input_controls|here]] for an example.
 </WRAP>

Orx Learning

User Tools

Site Tools

Differences

Page Tools