\nRunning RefactorScripts<\/a>
\nRefactorScript Window<\/a>
\nRefactorScript Language<\/a>
\nData Model<\/a>
\nCommon RefactorScripts<\/a><\/p>\n
<\/a>Overview<\/h2>\nRefactorScript is a mechanism for generating boilerplate code based on the existing C\/C++ structures or functions. The typical uses for RefactorScript are:<\/p>\n
\n- Automatically generating constructors or operators based on fields<\/li>\n
- Automatically generating NULL checks for functions<\/li>\n
- Automatically generating mock classes<\/li>\n
- Automatically generating implementations for function pointer fields<\/li>\n<\/ul>\n
RefactorScript is supported in VisualGDB Custom Edition and higher.<\/p>\n
<\/a>Running RefactorScripts<\/h2>\nThere are 2 ways of running a RefactorScript:<\/p>\n
\n- Selecting one or more classes, fields, methods, variables, etc. in Code Explorer -> Outline<\/a>, and using the Run RefactorScript<\/strong> button.<\/li>\n
- Using the smart tags directly in the code editor<\/li>\n<\/ol>\n
![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2021\/10\/run.png\")
<\/a><\/a>RefactorScript Window<\/h2>\nRunning a RefactorScript using either of the ways opens the RefactorScript window with the following controls:![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2021\/10\/wnd.png\")
<\/a><\/p>\n\n- The script selector (1)<\/strong> showing both the scripts shipped with VisualGDB (in C:\\Program Files (x86)\\Sysprogs\\VisualGDB\\RefactorScripts<\/strong>) and the user-defined scripts (stored in %LOCALAPPDATA%\\VisualGDB\\RefactorScripts<\/strong>).<\/li>\n
- Save<\/strong> and Save As<\/strong> buttons that allow saving the scripts (2)<\/strong>. Note that the scripts in Program Files<\/strong> cannot be modified, however creating a script with the same name under %LOCALAPPDATA%<\/strong> will automatically override the script from Program Files.<\/li>\n
- The instant update button (3) <\/strong>that controls whether the output is updated each time you edit the script. RefactorScript is designed to run very fast, so we recommend keeping this setting on.<\/li>\n
- The controls for the script arguments (4)<\/strong> automatically derived from the arguments to the main generator of the script.<\/li>\n
- Script input inspector showing the inputs passed to the main generator (5)<\/strong> and the properties of the selected element (6)<\/strong>.<\/li>\n
- The output from the current script (7)<\/strong> or a list of errors.<\/li>\n
- Buttons (8)<\/strong> for copying the script output to Clipboard, or inserting it in the code (the latter is only available when using SmartTags). You can also insert the results of running a RefactorScript by pressing Ctrl-Enter.<\/li>\n<\/ul>\n
The script editor provides very basic suggestion popups triggered by the ‘$’ and ‘.’ symbols:![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2021\/10\/suggestions.png\")
<\/a>The suggestion popups work by quickly running the script until the edited position. This ensures accurate results, but will not work for the code branches that are never executed (e.g. disabled via main generator arguments).<\/p>\n<\/a>RefactorScript Language<\/h2>\nRefactorScripts are an advanced form of code snippets. Lines prefixed with “>” are copied to the output, while expanding the $-expressions. Lines not prefixed with “>” follow C#-like syntax and are used to iterate over arrays, check conditions (e.g. skip non-pointers) and define intermediate variables.<\/p>\n
You can find a detailed description of the RefactorScript language on this page<\/a>.<\/p>\n<\/a>Data Model<\/h2>\nRefactorScripts can access exhaustive information about the selected classes, functions, fields or other C\/C++ entities, that can be used to fine-tune their output. You can easily explore this information via the right side of the RefactorScript window, or see our RefactorScript data model reference<\/a> for the full list of all provided fields.<\/p>\n<\/a>Common RefactorScripts<\/h2>\n
RefactorScript is supported in VisualGDB Custom Edition and higher.<\/p>\n
<\/a>Running RefactorScripts<\/h2>\nThere are 2 ways of running a RefactorScript:<\/p>\n
\n- Selecting one or more classes, fields, methods, variables, etc. in Code Explorer -> Outline<\/a>, and using the Run RefactorScript<\/strong> button.<\/li>\n
- Using the smart tags directly in the code editor<\/li>\n<\/ol>\n
<\/a><\/a>RefactorScript Window<\/h2>\nRunning a RefactorScript using either of the ways opens the RefactorScript window with the following controls:<\/a><\/p>\n\n- The script selector (1)<\/strong> showing both the scripts shipped with VisualGDB (in C:\\Program Files (x86)\\Sysprogs\\VisualGDB\\RefactorScripts<\/strong>) and the user-defined scripts (stored in %LOCALAPPDATA%\\VisualGDB\\RefactorScripts<\/strong>).<\/li>\n
- Save<\/strong> and Save As<\/strong> buttons that allow saving the scripts (2)<\/strong>. Note that the scripts in Program Files<\/strong> cannot be modified, however creating a script with the same name under %LOCALAPPDATA%<\/strong> will automatically override the script from Program Files.<\/li>\n
- The instant update button (3) <\/strong>that controls whether the output is updated each time you edit the script. RefactorScript is designed to run very fast, so we recommend keeping this setting on.<\/li>\n
- The controls for the script arguments (4)<\/strong> automatically derived from the arguments to the main generator of the script.<\/li>\n
- Script input inspector showing the inputs passed to the main generator (5)<\/strong> and the properties of the selected element (6)<\/strong>.<\/li>\n
- The output from the current script (7)<\/strong> or a list of errors.<\/li>\n
- Buttons (8)<\/strong> for copying the script output to Clipboard, or inserting it in the code (the latter is only available when using SmartTags). You can also insert the results of running a RefactorScript by pressing Ctrl-Enter.<\/li>\n<\/ul>\n
The script editor provides very basic suggestion popups triggered by the ‘$’ and ‘.’ symbols:<\/a>The suggestion popups work by quickly running the script until the edited position. This ensures accurate results, but will not work for the code branches that are never executed (e.g. disabled via main generator arguments).<\/p>\n<\/a>RefactorScript Language<\/h2>\nRefactorScripts are an advanced form of code snippets. Lines prefixed with “>” are copied to the output, while expanding the $-expressions. Lines not prefixed with “>” follow C#-like syntax and are used to iterate over arrays, check conditions (e.g. skip non-pointers) and define intermediate variables.<\/p>\n
You can find a detailed description of the RefactorScript language on this page<\/a>.<\/p>\n<\/a>Data Model<\/h2>\nRefactorScripts can access exhaustive information about the selected classes, functions, fields or other C\/C++ entities, that can be used to fine-tune their output. You can easily explore this information via the right side of the RefactorScript window, or see our RefactorScript data model reference<\/a> for the full list of all provided fields.<\/p>\n<\/a>Common RefactorScripts<\/h2>\n
<\/a><\/a>RefactorScript Window<\/h2>\nRunning a RefactorScript using either of the ways opens the RefactorScript window with the following controls:<\/a><\/p>\n\n- The script selector (1)<\/strong> showing both the scripts shipped with VisualGDB (in C:\\Program Files (x86)\\Sysprogs\\VisualGDB\\RefactorScripts<\/strong>) and the user-defined scripts (stored in %LOCALAPPDATA%\\VisualGDB\\RefactorScripts<\/strong>).<\/li>\n
- Save<\/strong> and Save As<\/strong> buttons that allow saving the scripts (2)<\/strong>. Note that the scripts in Program Files<\/strong> cannot be modified, however creating a script with the same name under %LOCALAPPDATA%<\/strong> will automatically override the script from Program Files.<\/li>\n
- The instant update button (3) <\/strong>that controls whether the output is updated each time you edit the script. RefactorScript is designed to run very fast, so we recommend keeping this setting on.<\/li>\n
- The controls for the script arguments (4)<\/strong> automatically derived from the arguments to the main generator of the script.<\/li>\n
- Script input inspector showing the inputs passed to the main generator (5)<\/strong> and the properties of the selected element (6)<\/strong>.<\/li>\n
- The output from the current script (7)<\/strong> or a list of errors.<\/li>\n
- Buttons (8)<\/strong> for copying the script output to Clipboard, or inserting it in the code (the latter is only available when using SmartTags). You can also insert the results of running a RefactorScript by pressing Ctrl-Enter.<\/li>\n<\/ul>\n
The script editor provides very basic suggestion popups triggered by the ‘$’ and ‘.’ symbols:<\/a>The suggestion popups work by quickly running the script until the edited position. This ensures accurate results, but will not work for the code branches that are never executed (e.g. disabled via main generator arguments).<\/p>\n<\/a>RefactorScript Language<\/h2>\nRefactorScripts are an advanced form of code snippets. Lines prefixed with “>” are copied to the output, while expanding the $-expressions. Lines not prefixed with “>” follow C#-like syntax and are used to iterate over arrays, check conditions (e.g. skip non-pointers) and define intermediate variables.<\/p>\n
You can find a detailed description of the RefactorScript language on this page<\/a>.<\/p>\n<\/a>Data Model<\/h2>\nRefactorScripts can access exhaustive information about the selected classes, functions, fields or other C\/C++ entities, that can be used to fine-tune their output. You can easily explore this information via the right side of the RefactorScript window, or see our RefactorScript data model reference<\/a> for the full list of all provided fields.<\/p>\n<\/a>Common RefactorScripts<\/h2>\n
<\/a><\/p>\n- \n
- The script selector (1)<\/strong> showing both the scripts shipped with VisualGDB (in C:\\Program Files (x86)\\Sysprogs\\VisualGDB\\RefactorScripts<\/strong>) and the user-defined scripts (stored in %LOCALAPPDATA%\\VisualGDB\\RefactorScripts<\/strong>).<\/li>\n
- Save<\/strong> and Save As<\/strong> buttons that allow saving the scripts (2)<\/strong>. Note that the scripts in Program Files<\/strong> cannot be modified, however creating a script with the same name under %LOCALAPPDATA%<\/strong> will automatically override the script from Program Files.<\/li>\n
- The instant update button (3) <\/strong>that controls whether the output is updated each time you edit the script. RefactorScript is designed to run very fast, so we recommend keeping this setting on.<\/li>\n
- The controls for the script arguments (4)<\/strong> automatically derived from the arguments to the main generator of the script.<\/li>\n
- Script input inspector showing the inputs passed to the main generator (5)<\/strong> and the properties of the selected element (6)<\/strong>.<\/li>\n
- The output from the current script (7)<\/strong> or a list of errors.<\/li>\n
- Buttons (8)<\/strong> for copying the script output to Clipboard, or inserting it in the code (the latter is only available when using SmartTags). You can also insert the results of running a RefactorScript by pressing Ctrl-Enter.<\/li>\n<\/ul>\n
The script editor provides very basic suggestion popups triggered by the ‘$’ and ‘.’ symbols:
<\/a>The suggestion popups work by quickly running the script until the edited position. This ensures accurate results, but will not work for the code branches that are never executed (e.g. disabled via main generator arguments).<\/p>\n<\/a>RefactorScript Language<\/h2>\n
RefactorScripts are an advanced form of code snippets. Lines prefixed with “>” are copied to the output, while expanding the $-expressions. Lines not prefixed with “>” follow C#-like syntax and are used to iterate over arrays, check conditions (e.g. skip non-pointers) and define intermediate variables.<\/p>\n
You can find a detailed description of the RefactorScript language on this page<\/a>.<\/p>\n
<\/a>Data Model<\/h2>\n
RefactorScripts can access exhaustive information about the selected classes, functions, fields or other C\/C++ entities, that can be used to fine-tune their output. You can easily explore this information via the right side of the RefactorScript window, or see our RefactorScript data model reference<\/a> for the full list of all provided fields.<\/p>\n
<\/a>Common RefactorScripts<\/h2>\n
- Save<\/strong> and Save As<\/strong> buttons that allow saving the scripts (2)<\/strong>. Note that the scripts in Program Files<\/strong> cannot be modified, however creating a script with the same name under %LOCALAPPDATA%<\/strong> will automatically override the script from Program Files.<\/li>\n