MapButton command: Difference between revisions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
{| | {| | ||
|width=" | |width="125px"| '''Action:''' | ||
|width=" | |width="775px"| | ||
<span class="f_Para">Lets you [[Reconfiguring GUI buttons and hot keys|assign a command to a Client button]] without having to edit a mapping file (</span><span class=" | <span class="f_Para">Lets you [[Reconfiguring GUI buttons and hot keys|assign a command to a Client button]] without having to edit a mapping file (</span><span class="term">ui.xml</span><span class="f_Para"> or </span><span class="term">uimore.xml</span><span class="f_Para">) and to restart the Client. </span> | ||
'''Syntax:''' | '''Syntax:''' |
Latest revision as of 23:00, 3 February 2023
Action: |
Lets you assign a command to a Client button without having to edit a mapping file (ui.xml or uimore.xml) and to restart the Client. Syntax: mapButton [buttonModifier-]buttonName command Where (case not important):
buttonModifier is optional, and its default is no modifier (command runs when you click the button).
Examples: mapButton button0 viewtext After you execute the command, the new mapping is reflected immediately in the button bar to which it applies. The new mapping does not appear in the mapping file. The new mapping does not survive a Client restart. The command to remove a button mapping is clearButton. The command to map a keyboard shortcut is mapKey. |
Client menu: | -- |
Introduced: | Build 56 |