Common tasks working with support and repair scripts and support and repair actions within a script
Jump to:
Working with scripts
Task | Steps |
---|---|
Create a new script |
From scratch
From an existing script
From a file
|
Save changes to a script |
Changes are not saved automatically. They are temporary until you save the changes.
Saving to registered scripts
Either method saves changes to the currently selected script. Registered scripts, or user-defined scripts available for selection in the dropdown menu, are stored in %APPDATA%\netfabb\repairscripts and %APPDATA%\netfabb\supportscripts, respectively. They are simple XML-flavored text files. Exporting to a file
|
Delete a script |
Note: Default scripts installed with
Netfabb cannot be deleted.
|
Reorder scripts in the selection |
|
Toggle visibility of built-in and custom scripts |
|
Working with actions
Task | Steps |
---|---|
Insert a new action |
Select an action from the dropdown menu and click Add. |
Delete an action |
Right-click the action and choose
|
Reorder actions |
Click the action you want to move and drag it onto the action you want it to come after. Note: To move an action to the top, drag it onto the topmost action, putting it in second place. Then drag the topmost action onto the second one.
Now available for repair scripts as well. |
Duplicate an action |
Right-click the action, then select
|
Execute an individual action in a script |
Double-click its green checkmark,
|
Export an action in its current configuration |
Right-click the action, then choose
Note: The filetype suffix for both individual actions and entire support scripts is SUPPORT. (Repair only)
|
Import an action |
Right-click anywhere in the
Support scripts view and choose
Note: You can import SUPPORT files holding individual actions as well as entire scripts. When a SUPPORT file contains an entire script, ALL of its actions are imported.
|
Disable/enable an action |
Right-click an action and choose
This function is useful to compare the effect of similar support actions but with a number of distinct differences that would otherwise be a great hassle to switch forth and back. The state of being enabled or disabled is also maintained during export and import. |
Rename an action |
Expand the action and click on the text field next to
While the action itself cannot be renamed, this adds a descriptive text next to its name that remains visible even when you collapse the action's node in the script tree. |