Configuring Controllers: Difference between revisions

Configuring Controllers (view source)

Revision as of 04:12, 17 December 2015

1,245 bytes removed , 17 December 2015

no edit summary

Lucario

6,576

edits

@@ Line 32: / Line 32: @@
 *Left click a slot to detect input, then press a button/key or axes on your selected device to save it to that slot.
 *Middle click a slot to clear it of inputs.
-*Right click a slot to show more input options.
+*Right click a slot to show more input options. See [[Input Syntax]] for documentation and examples.
@@ Line 70: / Line 70: @@
 *Left click a slot to detect input, then press a button/key or axes on your selected device to save it to that slot.
 *Middle click a slot to clear it of inputs.
-*Right click a slot to show more input options.
+*Right click a slot to show more input options. See [[Input Syntax]] for documentation and examples.
@@ Line 105: / Line 105: @@
 *Left click a slot to detect input, then press a button/key or axes on your selected device to save it to that slot.
 *Middle click a slot to clear it of inputs.
-*Right click a slot to show more input options.
+*Right click a slot to show more input options. See [[Input Syntax]] for documentation and examples.
-There is no way to map hotkeys on the native controllers.
+'''Background Input''' lets you use the controller or keyboard even if Dolphin isn't in focus.
-== Configure Controller Window ==
+With '''Iterative Input''' checked, it will turn the configuration window into sequence mode (I.E. once you click on a slot to set a button/key for it, it will start a sequence). As soon as you press a input on your device and it gets assigned, it will jump to the next slot for you to assign another input to, and it will keep going until the sequence is done.
-As found by right-clicking the button in GameCube, Wiimote, and Hotkey configuration windows.
-=== Parameters ===
+There is no way to map hotkeys on the native controllers.
-When opening Configuring Controller window the text cursor will be placed on beginning of lines in small text field.
-{| class="wikitable"
-|-
-! ''Detect''
-| It will automatically highlight the selected input in the list which can save your time looking through there. It will wait for input from the selected device in '''Device''' dropdown for 3 seconds.
-|-
-! ''Select''
-| Assigns the selected input from the list to the current text cursor location in small text field.
-|-
-! ''&#124; OR''
-| Similar to '''''Select''''', it types "<var> &#124; </var>" before a selected input.
-|-
-! ''& AND''
-| Similar to '''''Select''''', it types "<var> & </var>" before a selected input.
-|-
-! ''! NOT''
-| Similar to '''''Select''''', it types "<var>!</var>" before a selected input.
-* This is one confusing part, requires additional combination and/or manual editing in the text field. Check the [[#! NOT]] example in next section.
-|-
-! ''+ ADD''
-| Similar to '''''Select''''', it types "<var> + </var>" before a selected input.
-|}
-=== Parameter Examples ===
-<pre>Guide | `DInput/0/Keyboard Mouse:RMENU` & `DInput/0/Keyboard Mouse:RETURN`</pre>
-For some reason the first two parameters don't work.
-<pre>`Shoulder L` & Guide | `DInput/0/Keyboard Mouse:RMENU` & `DInput/0/Keyboard Mouse:RETURN`</pre>
-==== ! NOT ====
-Command will always active unless this input is triggered.
-<pre>!`Pad W`</pre>
-Command will active when Button X is pressed, but it won't be triggered when Pad W is also pressed.
-<pre>!`Pad W` & `Button X`</pre>
-The first two parameters will not work anymore.
-<pre>!`Pad W` & `Button X` | !`Pad E` & `Button B`</pre>
-However this will work alright.
-<pre>`Button X` & !`Pad W` | `Button B` & !`Pad E`</pre>
 [[Category:Tutorials]]