diff options
Diffstat (limited to 'system/keymaps/customcontroller.AppleRemote.xml')
| -rw-r--r-- | system/keymaps/customcontroller.AppleRemote.xml | 65 |
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"> |