Tornado not only allows you to customize the appearance of the display to match your preferences, but it also allows you to add menu entries for other tools you may wish to use. The Options entry in the Tools menu displays commands that change the fonts, colors, editor settings, and other defaults for Tornado. The Customize entry in the Tools menu opens a dialog box for adding menu items.

Use the View>Toolbars menu item to customize the toolbars that are displayed in the IDE. All toolbars can be floating or docked. Each menu item acts as a toggle to display or hide the specified toolbar. The options are:

Standard Windows functions including Open, Save, Cut, Paste, and Print.

Launch the browser, the shell, the debugger, the simulator, WindView, and triggering.

Debugger functions including start debugging, run a function, step, and watch.

WindView zoom functions, filtering, and numerical analysis.

Build, compile current file, update dependencies, and download.

Use the View>Status Bar menu item to toggle display of the status bar at the bottom of the Tornado window.

You can specify the various default options that Tornado uses through the Options entry in the Tornado Tools menu.

The Download page provides options for handling symbols when objects are downloaded to the target (Figure 12-1).

The options are as follows:

The system symbol table offers two check box options:

LOAD_LOCAL_SYMBOLS

Only local symbols are added to the system symbol table

LOAD_GLOBAL_SYMBOLS (default)

Only external symbols are added to the system symbol table

In order to obtain the other symbol options, you can:

• Check nothing, the equivalent of LOAD_NO_SYMBOLS, which adds no symbols to the system symbol table.

• Check both boxes, the equivalent of LOAD_ALL_SYMBOLS, which adds all symbols to the system symbol table.

The common symbol resolution options are mutually exclusive.

LOAD_COMMON_MATCH_NONE

Allocate common symbols, but do not search for any matching symbols (the default)

LOAD_COMMON_MATCH_USER

Allocate common symbols, but search for matching symbols in user-loaded modules

LOAD_COMMON_MATCH_ALL (default)

Allocate common symbols, but search for matching symbols in user-loaded modules and the target-system core file

The C++ constructors options are mutually exclusive:

LOAD_CPLUS_XTOR_AUTO (default)

C++ ctors/dtors management is explicitly turned on

LOAD_CPLUS_XTOR_MANUAL

C++ ctors/dtors management is explicitly turned off

LOAD_HIDDEN_MODULE (not default)

Load the module but make it invisible to WTX_MSG_MODULE_LIST

The Set Defaults buttons resets the options to their defaults.

Select Options in the Tools menu, then click the Editor tab to adapt the editor to your preferences. The Editor page is shown in Figure 12-2.

The following choices are available on the Editor page:

The Horizontal and Vertical Scrollbar check boxes control which scroll bars appear in the editor window. If no scroll bars appear, you can only scroll by using the keyboard arrow keys to move past the displayed area (or by typing past the displayed area). Defaults: Vertical on, Horizontal off.

When Attribute Pane is checked (the default), Tornado reserves space in the left margin of source-code editor windows and displays state information there: breakpoint locations, the currently executing line, the current error, and the like. When Attribute Pane is not checked, Tornado conveys this information instead by highlighting entire lines in the editor window.

The editor uses regularly spaced tab stops; this field controls how far apart the tab stops are. If you use tabs for code indentation, smaller values in this field are useful in small windows. Default: 8.

The editor keeps track of your changes to the source file, and uses this information to allow you to reverse those changes (through the Undo command in the Edit menu). This box specifies how many changes the editor keeps track of, up to a maximum of 512 changes. Default: 512.

This panel contains two check boxes for different purposes. Both check boxes are on by default.

When Save before running Tools/Builds is checked, Tornado saves all modified text from the current editor windows before executing any command from the Tools or Project menus.

When Automatic reload of externally modified files is checked, Tornado automatically reloads any file that is modified by an external editor. This keeps the Tornado tools synchronized with an external editor.

The radio buttons in this panel can be used to determine the end-of-line format for the files you edit. The Tornado editor always saves files with a consistent end-of-line format, converting any inconsistent formats, if necessary. The DOS end of line format is a combination of carriage return and line feed. The UNIX end-of-line format is a line feed. The Automatic option preserves whatever format is present in existing files when they are opened, and uses DOS format for new files.

If you are accustomed to another editor, you may want to use Tornado only as a viewer and to provide debugging context, and pass control to your preferred editor when you want to make changes to a file. Select Options in the Tools menu, then click External Editor to specify an editor other than the Tornado editor. The External Editor page is shown in Figure 12-3.

The following choices are available on the External Editor page:

The Command line text box allows you to enter the command that invokes your preferred editor. Click the button at the right of the box to see menu including a browse option and macros which allow you to capture Tornado context in your commands (File name and Line number). See Macros for Customized Menu Commands for explanations of these macros.

The Defaults list box allows you to select from several available alternative editors. When you make a selection, the appropriate command is automatically entered in the Command line text box.

The Invoke from section of the page allows you to choose where your external editor will be invoked. For example, if you check File menu but not Project, selecting Open from the File menu will open the file in your external editor, but double-clicking on a file in the Project window will open the file in the Tornado editor.

Select Options in the Tools menu, then click Projects to specify certain project attributes. The Projects page is shown in Figure 12-4.

The following choices are available on the Projects page:

Checking the Enable extended Build Options box causes Standard BSP Builds to be added to the Build tab. For more information on command-line builds, see 5. Command Line Configuration and Build.

Checking the Show advanced component properties box adds the Definition tab to the component property window. The Definition page shows the internal schema and attributes for the component. This may be helpful for authoring or debugging components.

The Build Environment Variables section displays two environment variables, WIND_SOURCE_BASE and WIND_PROJ_BASE, that provide flexibility in locating and sharing project files. In most cases these variables are not needed. For information on when you might need them and how to use them, see Sub-Projects.

For example, using Tornado 1.0.1-style Build menu customizations, you can add a command that compiles the default make target in the same directory as the file currently open or selected in the Project tool. Use the $filepath macro in Working Directory and leaving Build Target blank in the Customize Builds dialog box.

If your organization uses a source-control (sometimes called configuration management) system to manage changes to source code, you probably need to execute a command to "check out" a file before you can make changes to it. Select Options in the Tools menu, then click Version Control to create commands to automatically check out or check in an open file using your version control system. The Version Control page is shown in Figure 12-6.

The following choices are available on the Version Control page:

The Checkin text box allows you to enter the command that checks a file in to your version control system. The button at the end of the box opens a pop-up menu which has a Browse item to help you locate the command and macros to provide the Tornado context (see Table 12-1).

The Checkout text box allows you to enter the command that checks a file out of your version control system. The button at the end of the box opens a pop-up menu which has a Browse item to help you locate the command and macros to provide the Tornado context (see Table 12-1).

Table 12-1:   Macros for Version Control

Figure 12-7:   Modify Comment Window

Selecting an item from the Defaults drop-down list box automatically fills in the appropriate commands for the selected version control system.

Clicking the Advanced button opens the Customize Tools dialog box, which can be used to put commands on the Tools menu. Anything that can not be done on the Version Control page can be done on the Customize Tools dialog box.

Commands created with the Checkin and Checkout text boxes appear on the pop-up menu accessed by right-clicking on the source file in the Tornado Editor window or the Project window.

Select Options in the Tools menu, then click Fonts/Colors to change the fonts and colors that Tornado uses for all text windows: the editor window, the shell, and the debugger command window. The Fonts/Colors page is shown in Figure 12-8.

The Font selection boxes allow you to select a typeface, weight, and size in points. Different fonts are appropriate for different working environments: for example, usually a smaller point size is more desirable on a lap-top than on a large desktop display. The Sample box shows you what your selections will look like.

If you check the Syntax Coloring box, Tornado will identify various distinguished window elements by color, including syntactically distinguished text and the attribute-panel markers that appear during debugging.

You can choose which window element to color by clicking an entry in the Items list box. Table 12-2 describes the window elements available for coloring. The Foreground Color and Background Color panels allow you to control the foreground and background independently for each window element; click on the desired color in either list to assign that color to the currently selected window element.

You can always return to the original settings by clicking the following buttons:

Reset the currently selected window element to its default color.

Reset all window elements to their default colors.

Select Options in the Tools menu, then click Debugger to customize various debugger attributes. The Debugger page is shown in Figure 12-9.

The following choices are available on the Debugger page:

Checking the Hexadecimal display box forces all debugger window displays to hexadecimal. The default is to display the format chosen by gdb for each window.

Checking the Docking views box causes all debuggers windows to dock. The default is floating windows.

Use the Format and Size drop-down combo boxes to select how the memory window is displayed.

Checking the Always refresh on debugger stop box causes the memory window to update whenever execution stops. This is the default. For performance reasons you may choose to uncheck the box and only update it on demand.

Allows you to determine the degree to which the debugger automatically attaches to a task that throws an exception. Depending on which option you select, the behavior is as follows:

• Never: the debugger never automatically attaches to the task throwing the exception.

• Only if not already attached: The debugger attaches to the task if you are not already attached to another task.

• Always: the debugger always automatically attaches to the task throwing the exception.

Select Options in the Tools menu, then click Tornado Registry to change the Tornado registry. The Tornado Registry page is shown in Figure 12-10.

A local registry resides on your local host. It lists any target servers you have running on your host. If others are using your machine as a remote registry, their target servers will also appear on the list; otherwise only your local target servers are known to Tornado.

A remote registry resides on another host. All your target servers and any other networked target servers known to that registry are listed. You can specify either the host name or the IP address of the remote host.

Press one of the buttons to launch the Tornado SETUP program. You can change the following settings that you specified from Setup when you installed Tornado:

• Reconfigure Registry

• Register File Types

• Reconfigure Licensing

You can add entries to the Tools menu to allow easy access to additional tools. Before you add any commands in this part of the menu, Tornado displays the placeholder No Custom Tools as a disabled menu entry. The Customize command in the Tools menu allows you to add (or remove) entries at the end of the Tools menu.

Click Customize in the Tools menu to open the Customize Tools dialog box (Figure 12-11).

The Menu Contents list box in the Customize Tools dialog box shows all custom commands currently in the Tools menu. When you select any item in this list, you can edit its attributes in the three text boxes near the bottom of the dialog box.

The Customize Tools dialog box has the following buttons:

Activates the list and check boxes at the bottom of the Customize Tools dialog box and enters New Tool in the Menu Text list box. Replace New Tool with the command description; when you click OK, the new menu item appears in the Tools menu.

Deletes the selected menu item from the Tools menu.

Moves the selected menu item up one line in the Menu Contents list box and changes the displayed order on the Tools menu.

Moves the selected menu item down one line in the Menu Contents list box and changes the displayed order on the Tools menu.

Applies your changes to the Tools menu.

Discards your changes without modifying the Tools menu.

The three text boxes near the bottom of the Customize Tools dialog box allow you to specify or change the attributes of a custom command.

Contains the name of the custom command, as it appears in the Tools menu.

Specifies the instructions to execute your command. You can place anything here that you could execute at the command prompt or in a batch file. Click the button at the right of the box to see a pop-up menu including a browse option and a list of macros which allow you to capture Tornado context in your commands. See Macros for Customized Menu Commands for explanations of these macros.

Use this field to specify where (in what directory) to run the custom command. You can edit the directory name in place, or click the button at the right of this field to bring up a menu similar to the Tool Command menu. It includes a directory browser where you can search for the right directory and the same list of macros. To use the Tornado working directory, leave this field blank.

At the bottom of the Customize Tools dialog box are the following check boxes:

• Prompt for Arguments

When this box is checked, Tornado prompts for command arguments using a dialog box, when you click the new command. The command line is displayed in a window where you can add additional information. (See Figure 12-12.)

Figure 12-12:   Command Line Arguments Dialog Box

The pop-up menu opened by the buttons to the right of the text boxes provides several macros for your use in custom menu commands. These macros allow you to write custom commands that are sensitive to the context in the editor, or to the global Tornado context. For example, there are macros for the full path of the file in the active editor window, and for useful fragments of that file's name. Table 12-3 lists macros for editor context; in this table, the phrase active file refers to the file that is open in the active editor window (or selected in the project facility if no editor window is open).

Table 12-4 lists macros for the project facility context.

Table 12-5 lists macros for the global Tornado context.

These macros are available for custom entries in the Build menu as well as for the Tools menu. For information on making them available though the Build menu, see 12.3.4 Project. For information on using them for custom builds, see 12.4.3 Customizing the Build Menu.

This example illustrates how to use the Customize Tools dialog box to add an Uncheckout command to the Tools menu: the command cancels the checkout of whatever file is currently open in Tornado (that is, the file visible in the current editor window). Figure 12-13 illustrates the specification for a ClearCase command to uncheckout a module.

The Menu Text entry indicates that the command unchecks out a file, but is not specific to any particular file. The Tool Command field uses the $filepath macro (Macros for Customized Menu Commands) to expand the current file to its full path name.

In this example, the Prompt for Arguments box is checked. When the new Uncheckout command in the Tools menu is executed, the predefined argument list appears as a default in a dialog box (shown in Figure 12-14), to permit specifying other arguments if necessary.

Figure 12-15 illustrates the specification for a command to run the Windows Notepad editor on the file that is currently open in Tornado. The Menu Text contains a useful name, while the Tool Command field uses the actual execution command and $filepath to identify the current file. In this case, Prompt for Arguments is not checked; thus the editor runs immediately.

Normally you would change the default editor to an external editor using the External Editor tab under Tools>Options. In the case where you only wish to use an alternate editor some of the time, you may prefer this method.

Tornado includes a suite of software-development utilities described in the GNU ToolKit User's Guide: The GNU Binary Utilities. If you execute any of these utilities frequently, it may be convenient to define commands in the Tools menu for that purpose.

Figure 12-16 illustrates the specification for a command to run the sizearch utility, which lists the size of each section of an object module for target architecture arch. In this case, the Tool Command field uses $filedir/SIMNTgnu/$basename to construct the path and name of the object file generated from the current source file The Working Directory field is filled in using the browse option to locate the appropriate version of sizearch in the correct directory.

You can add a Tools command to link your Web browser directly to announcements from Wind River (and to related Internet resources). Figure 12-17 shows the specification for a Wind River Web Page command. (For a description of the information available on the Wind River home page, see 1.6 Customer Services.

Tornado itself does not include a Web browser. If you do not have a Web browser, or your system does not have direct Internet access, ignore this example; it provides convenient access to information, but no essential functionality.

If you are using Tornado 1.0.1 build techniques, you can add commands to the Build menu to build any object that can be generated using make. Typically this requires first generating (or writing) a makefile that specifies the rules to build that object. It also requires checking Show Tornado 1.0.1 menu items on the Project tab of the Tools>Options menu (see 12.3.4 Project).

Once a makefile is in place, click Customize in the Build menu to add your own commands to the bottom part of that menu (or to remove commands you no longer need). The Customize Builds dialog box appears (Figure 12-18). This dialog box shows all custom entries already present in the Project menu (if any), and allows you to add commands to, remove commands from, or reorder the list of custom Project commands.

The Customize Builds dialog box has the following buttons:

Activates the list and check boxes at the bottom of the Customize builds dialog box and enters New Build in the Menu Text list box. Replace New Build with the command description; when you click OK, the new menu item appears in the Build menu.

Deletes the selected menu item from the Build menu.

Moves the selected menu item up one line in the Menu Contents list box and changes the displayed order on the Build menu.

Moves the selected menu item down one line in the Menu Contents list box and changes the displayed order on the Build menu.

Applies your changes to the Build menu.

Discards your changes without modifying the Build menu.

The Menu Contents list box in Customize Builds shows all custom commands currently in the Build menu. When you select any item in this list, you can edit its attributes in the three text boxes near the bottom of the dialog box:

Contains the name of the custom command, as it appears in the Build menu.

You can specify any information here that can be placed in the make command line. You must specify at least the name of the object to build, but frequently it is also useful to include additional parameters in some of the standard makefile variables (see VxWorks Programmer's Guide: Configuration and Build).

Click the button at the right of the box to see a pop-up menu including a browse option and a list of macros which allow you to capture Tornado context in your commands. See Macros for Customized Menu Commands for explanations of these macros.

Use this field to specify the directory containing the makefile that defines the rules for building this target. (Usually, this directory is also where the source code for the object resides, and where the new object is generated.) You can edit the directory name in place, or click the button at the right of this field to bring up a menu similar to the Build Target menu. It includes a directory browser where you can search for the right directory and the same list of macros. To use the Tornado working directory, leave this field blank.

You can also use the browse feature to select makefiles with names other than the names recognized by default, Makefile or makefile; Tornado inserts the make -f option automatically when you select a makefile with another name). If you use the Browse button without filling out the Build Target field, the new command is labeled Makefile, and it builds the default target in the makefile you selected.

When Tornado begins executing, it checks for initialization files of the form .wind\filename.tcl in two places: first under c:\tornado (that is, in the directory specified by the WIND_BASE environment variable), and then in the directory specified by the HOME environment variable (if that environment variable is defined). If any files are found, their contents are sourced as Tcl code when Tornado starts.

The Tornado.tcl file allows you to customize the Tools menu and tool bar, as well as other elements of the Tornado window. For example, you can have your own dialog box appear based on a menu item you add to any menu. For more information about the Tcl customization facilities available, see the Tornado API Programmer's Guide or the online Tornado API Reference.

The windHelp.tcl file allows you to specify a different HTML browser. The default is NetScape Communicator. To change the default, create windHelp.tcl with the following contents:

set htmlBrowser "newbrowser -install"