System Tools is collection of visual editors that allow the everyday Surpac user to leverage tricks usually restricted to the realm of the power user. They provide an easy means to add, edit, and delete system configuration items in Surpac that usually have to be done using a text editor like notepad.
The various System Tools will ensure correct syntax is maintained in the Surpac configuration files. Functions are included to
- Manage logicals definitions
- Define hotkeys (F1 – F12)
- Define command aliases (shortcuts)
- Create Surpac range files
- Define portable database definitions
The logicals editor provides an interface to manage logicals definition’s in Surpac. Logicals can exist in the standard SSI_ETC:Logicals.ssi file or a user defined logcals file. The editor also provides tools to check for duplicate logical definitions and also to check that the defined directory paths exist.
The hotkey editor provides an easy system to define your keyboard hotkeys F1 through to F12. Hotkeys can be setup to run an internal Surpac action or command but can also be setup to run a macro.
Command Alias Editor
The command alias editor allows you to manage up to 10 alias files. A command alias is a shortcut system in Surpac that allows the user to define short names (an alias) to a longer command name. For example the shortcut BD maps to the Surpac command Bearing and Distance.
Command Alias Integrity Checker
The command alias integrity checker is a tool that performs checks on your defined command aliases. The following three checks can be made
- Check for duplicate alias names
- Check for invalid command names
- Checking for missing macro/script files
Range File Editor
This function allows you to define Surpac range files that you can later use in any Surpac input field that accepts a range value. Simple specify @myrangefile where myrangefile is name of the range file in the input field
Create Portable Database Definition
In order to access databases from any directory you are required to enter the full directory path into the ddb file as part of the DB_SPECIFIC clause. This function improves on this by inserting a logical definition instead and creating the logical if required.
Please visit the following links for further information on System Tools and related topics