Client Command Reference: Difference between revisions
(Created page with "__TOC__ <span class="f_Para">Client commands are the operations that you invoke from Client menus and can assign to a button, keyboard shortcut, or macro. It is intended that...") |
No edit summary |
||
| Line 6: | Line 6: | ||
<span class="f_Para">Later sections in this document describe ways to use the commands: </span> | <span class="f_Para">Later sections in this document describe ways to use the commands: </span> | ||
*[[ | *[[Reconfiguring GUI buttons and hot keys|Reconfiguring GUI buttons and hot keys]] describes how you can map any command to a Client button or hot key. </span> | ||
*[[ | *[[Default settings of buttons and hot keys|Default settings of buttons and hot keys]] lists the default hot keys and buttons with which some of these commands are associated. | ||
*[[ | *[[Using Debugger Macros|Using Debugger Macros]] describes how you can use </span><span class="f_Para">script multiple commands to run consecutively</span><span class="f_ListBul1">. </span> | ||
A very few of the commands are '''macro only''': commands that may be used only in a Debugger macro. The descriptions of these commands include a <var>Scope</var><span class="f_Para"> section that reminds of this restriction. </span> | |||
<span class="f_Para">As a quick means of testing what a command does, you can open the </span>< | <span class="f_Para">As a quick means of testing what a command does, you can open the </span><var>[[using_macro_console_cmdline.html#macro_command_line|Command Line]]</var><span class="f_Para"> tool and run your command from there (specifying a qualifying </span><var>Command</var><span class="f_Para"> keyword if a same named macro command exists). For informational, error, and trace messages from the command, you can use the [[using_macro_console_cmdline.html#macro_console|Console]] tool. </span> | ||
<span class="f_Para">You can also execute a command from within a User Language request by using the </span>< | <span class="f_Para">You can also execute a command from within a User Language request by using the </span><var>ClientCommand</var><span class="f_Para"> method of the [[using_debuggertools_obj.html|DebuggerTools]] class. </span> | ||
[[Category:Debugger Home]] | [[Category:Debugger Home]] | ||
Revision as of 01:55, 20 September 2022
Client commands are the operations that you invoke from Client menus and can assign to a button, keyboard shortcut, or macro. It is intended that there be a command available for any Client operation you want to automate.
The following subsections describe individually the available commands, which are specified without regard for case.
Later sections in this document describe ways to use the commands:
- Reconfiguring GUI buttons and hot keys describes how you can map any command to a Client button or hot key.
- Default settings of buttons and hot keys lists the default hot keys and buttons with which some of these commands are associated.
- Using Debugger Macros describes how you can use script multiple commands to run consecutively.
A very few of the commands are macro only: commands that may be used only in a Debugger macro. The descriptions of these commands include a Scope section that reminds of this restriction.
As a quick means of testing what a command does, you can open the Command Line tool and run your command from there (specifying a qualifying Command keyword if a same named macro command exists). For informational, error, and trace messages from the command, you can use the Console tool.
You can also execute a command from within a User Language request by using the ClientCommand method of the DebuggerTools class.