aboutsummaryrefslogtreecommitdiff
path: root/system/keymaps/customcontroller.AppleRemote.xml
diff options
context:
space:
mode:
authorNed Scott <ned@nedscott.com>2016-08-27 00:37:58 -0700
committerNed Scott <ned@nedscott.com>2016-09-18 16:52:32 -0700
commit9719da3ea8046d363f3ebf650368ce7ef0838ed3 (patch)
tree4c51c85735cf908344859bdf6441f8f3c36e6780 /system/keymaps/customcontroller.AppleRemote.xml
parenta56be14886528adb567e0f0a1fc7a3c5a63c92f4 (diff)
Miscellaneous keymap cleanup
These are all the little things that didn't seem big enough for their own PR: Updated the header area to finally remove all those lingering XBMC references (some even mentioned the xbox!) touchscreen.xml - Removed two-finger-swipe-left = seek(-7). It will now always be "back". This was originally added when remote.xml used to do smallstepback, but JMarshall thought back should always be back, and I agree. I just forgot to change touchscreen.xml Joystick keymap had an unneeded < programs > section that was left over from a previous fix. Added a couple of mod-combo actions to keyboard.xml for the sake of users who can't use longpress (Flirc, etc).
Diffstat (limited to 'system/keymaps/customcontroller.AppleRemote.xml')
-rw-r--r--system/keymaps/customcontroller.AppleRemote.xml65
1 files changed, 36 insertions, 29 deletions
diff --git a/system/keymaps/customcontroller.AppleRemote.xml b/system/keymaps/customcontroller.AppleRemote.xml
index 4a47364c89..46d7d3e1dc 100644
--- a/system/keymaps/customcontroller.AppleRemote.xml
+++ b/system/keymaps/customcontroller.AppleRemote.xml
@@ -1,33 +1,40 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- This file contains the mapping of keys (gamepad,remote and keyboard) to actions within XBMC -->
-<!-- The <global> section is a fall through - they will only be used if the button is not -->
-<!-- used in the current window's section. Note that there is only handling -->
-<!-- for a single action per button at this stage. -->
-<!-- For joystick/gamepad configuration under linux/win32, see below as it differs from xbox -->
-<!-- gamepads. -->
-
-<!-- The format is: -->
-<!-- <device> -->
-<!-- <button id=""#>xbmc action</button> -->
-<!-- </device> -->
-
-<!-- To map keys from other remotes using the RCA protocol, you may add <customcontroller name="AppleRemote"> blocks -->
-<!-- In this case, the tags used are <button id=""#> where # is the original button code (OBC) of the key -->
-<!-- You set it up by adding a <customcontroller name="AppleRemote"> block to the window or <global> section: -->
-<!-- <customcontroller name="AppleRemote"> -->
-<!-- <button id="45">Stop</button> -->
-<!-- </customcontroller> -->
-
-<!-- Note that the action can be a built-in function. -->
-<!-- eg <button id="6">ActivateWindow(Favourites)</button> -->
-<!-- would bring up Favourites when the button with the id of 6 is press. In this case, "Menu" -->
-
-<!-- -->
-<!-- Button Ids: -->
-<!-- 'id' is the button ID used by SDL. The key ids recognized from your remote appears -->
-<!-- in /var/log/syslog on the ATV2 for each button pressed and when debug mode is enabled -->
-<!-- Use your log to discover and map custom buttons to actions. -->
-
+<!-- This file contains the mapping of keys to actions within Kodi. -->
+<!-- -->
+<!-- The format is: -->
+<!-- <window> -->
+<!-- <device> -->
+<!-- <button>action</button> -->
+<!-- </device> -->
+<!-- </window> -->
+<!-- -->
+<!-- The <global> section is a fall through - they will only be used if the button is -->
+<!-- not used in the current window's section. -->
+<!-- -->
+<!-- Actions can be built-in functions. -->
+<!-- eg <button id="6">ActivateWindow(Music)</button> -->
+<!-- would automatically go to Music on the press of the "Menu" button. -->
+<!-- -->
+<!-- -->
+<!-- An empty action removes the corresponding mapping from default and parent keymaps. -->
+<!-- This is different from a "noop" action, which disables a button. -->
+<!-- -->
+<!-- More documentation on keymaps can be found on http://kodi.wiki/view/keymaps -->
+<!-- -->
+<!-- To map keys from other remotes using the RCA protocol, you may add -->
+<!-- <customcontroller name="AppleRemote"> blocks. -->
+<!-- In this case, the tags used are <button id=""#> where # is the original button code -->
+<!-- (OBC) of the key. -->
+<!-- You set it up by adding a <customcontroller name="AppleRemote"> block to the window -->
+<!-- or <global> section: -->
+<!-- <customcontroller name="AppleRemote"> -->
+<!-- <button id="45">Stop</button> -->
+<!-- </customcontroller> -->
+<!-- -->
+<!-- Button Ids: -->
+<!-- 'id' is the button ID used by SDL. The key ids recognized from your remote appears -->
+<!-- in the log file for each button pressed and when debug mode is enabled. -->
+<!-- Use your log to discover and map custom buttons to actions. -->
<keymap>
<global>
<customcontroller name="AppleRemote">