This section describes the preference panels that control general IDE features:

• Build Settings
• IDE Extras
• Plugin Settings
• Shielded Folders
• Source Trees

The Build Settings preference panel, shown in Figure 8.3, allows you to customize project builds.

Use this pop-up menu to determine how the CodeWarrior IDE handles project builds. You can choose to Always build projects before running them, Never build projects before running them, or let the CodeWarrior IDE Ask you how to proceed.

Enable this checkbox to automatically save all open files before executing the following commands: Preprocess, Precompile, Compile, Disassemble, Bring Up To Date, Make, and Run.

Enable this checkbox to display a message after building an up-to-date project. The Message window displays the message. For more information about this window, see "Guided Tour of the Message Window". For more information about up-to-date projects, see "Updating a Project".

After loading a project file, the IDE creates or updates an associated project data folder. The IDE stores intermediate project data in this folder. After you build or close the project, the IDE uses the information in the project data folder to update the project file.

By default, the IDE places the project data folder within the same folder as the project file. However, the IDE cannot create or update a project data folder in a location that grants read-only privileges.

To specify a different location for the project data folder, enable the Use Local Project Data Storage checkbox, then click Choose to select the path to the location you wish to use. For more information about the types of paths available to you, see "Add".

Enable this checkbox to play a sound after finishing a build of your project. You can choose different sounds for successful and unsuccessful builds by using the Success and Failure pop-up menus, respectively.

Use the Compiler thread stack field to specify the upper limit of stack size allocated by the IDE for compiling and linking thread support.

All builds in CodeWarrior are threaded, with compiling and linking occurring on a thread separate from the main application thread. This setting lets you control the size of the stack allocated for the compiler thread.

Normally, you should not change this setting. However, if you have a large or very complex project, you can increase this setting to avoid compiler crashes.

This field, shown in Figure 8.3, specifies the upper limit on how much memory the IDE should use for caching #include files and precompiled headers. If your computer has substantial memory and you want to use that memory to accelerate builds, increase the number in this field.

The IDE Extras preference panel, shown in Figure 8.4 (Windows) and Figure 8.5 (Mac OS), includes options for remembering previously opened projects and text files, as well as configuring the IDE for use with third-party editors.

The IDE Extras preference panel also lets you configure miscellaneous options, such as window zooming and the Scripts menu.

Use this pop-up menu to choose the default menu bar layout for the CodeWarrior IDE. The name of the menu bar layout suggests the host. For example, use the Windows menu bar layout to organize IDE menus according to Microsoft¨ Windows¨ user-interface standards. "CodeWarrior¨ IDE Menu Reference" shows the organization of the menu commands under each menu bar layout.

Enter in this field the maximum number of recent projects that you want displayed in the Open Recent submenu of the File Menu.

Type in this field the maximum number of recent documents that you want displayed in the Open Recent submenu of the File Menu.

Enter in this field the minimum length of time to hold down the mouse button before the IDE's contextual menus appear. You can enter a value from 0 to 240 ticks. Each tick represents 1/60th of a second (16.67 milliseconds). For general information about contextual menus, see "Using the Contextual Menu". To learn how to configure the types of commands that appear in the contextual menus, see "Contextual Menus".

This checkbox configures the behavior of the zoom box in the upper right-hand corner of all editor windows. If you enable this checkbox, clicking the zoom box of an editor window resizes that window to fill the entire screen. If you disable the checkbox, clicking the zoom box of an editor window resizes that window to a standard size.

Enable this checkbox to display the Scripts menu in the IDE's menu bar. For more information about scripting the IDE, refer to the CodeWarrior Scripting Reference. For more information about scripting the IDE with AppleScript, refer to Targeting Mac OS.

Enable this checkbox to use a third-party text editor to modify text files. Disable the checkbox if you wish to use the CodeWarrior editor.

Enabling the Use External Editor checkbox causes the CodeWarrior IDE to send Open Document ('odoc') AppleEvents to AppleScript-compatible third-party text editors. To use this feature, create a (Helper Apps) folder (if it does not already exist) in the CodeWarrior IDE application folder. Next, place an alias inside the (Helper Apps) folder that points to your third-party editor application. Then, change the name of the alias to External Editor.

To learn how to add files to the Project window, see "Adding Files."

Enable this checkbox to use a third-party text editor to modify text files. Disable the checkbox if you wish to use the CodeWarrior editor.

If you use a third-party text editor, you can enter command lines in the following fields:

• Launch Editor-specifies the text editor that the IDE should use to display text files
• Launch Editor w/ Line #-specifies a text editor and an initial line of text to jump to upon launch

You can use two variables in the command-line strings:

For example, if you want to use the Emacs text editor to edit text files, then you would enter the following command line in the Launch Editor field:

If you also want the text editor to jump to a particular line in the text file, you would type the following command line in the Launch Editor w/ Line # field:

Consult the documentation provided with your third-party text editor for more information about using command lines.

This checkbox configures the interface style used by the IDE:

• MDI (Multiple Document Interface)-Under this interface style, the IDE uses a main application window. Multiple IDE document windows appear within the IDE's main application window. Enable the checkbox to use this interface style.
• FDI (Floating Document Interface)-Under this interface style, the IDE does not use a main application window. Multiple IDE document windows "float" above the desktop. Disable the checkbox to use this interface style.

This checkbox toggles the appearance of the ToolServer menu (Figure 8.6) in the IDE's menu bar. For more information about ToolServer, refer to Targeting Mac OS.

This checkbox toggles the appearance of Balloon Help for the toolbar icons. With automatic toolbar help enabled, as you rest the cursor over a toolbar icon, a help balloon appears and names the command represented by that icon.

This checkbox toggles the appearance of the BBEdit Extensions menu (Figure 8.7) in the IDE's menu bar. This menu allows you to use the IDE to access BBEdit extensions. For more information about BBEdit, refer to its documentation.

Use this pop-up menu to select an online database application to look up references and definitions. Although they are not included in your CodeWarrior product, the IDE supports the following formats:

• QuickHelp-based documents
• Symantec THINK Reference database
• PalmQuest reference for the Palm connected organizer
• QuickView-based documents, such as the Macintosh Programmer's Toolbox Assistant (MPTA)

The Plugin Settings preference panel, shown in Figure 8.8, contains options for troubleshooting third party IDE plug-ins.

Use this pop-up menu to determine the amount of information reported for the IDE plug-ins that you develop. This information is useful for diagnosing plug-in behavior, or for viewing detailed information about the properties of installed plug-ins.

Use the Level pop-up menu to report one of the following levels of plug-in diagnostic information:

• None-This level is selected by default. The IDE does not activate the plug-in diagnostics at this level. Consequently, the IDE does not produce output at this level.
• Errors Only-Choose this level to report problems that the IDE encounters when loading plug-ins. These problems appear in a new text file after the IDE starts up
• All Info-Choose this level to report detailed information for each installed plug-in. The IDE reports problems with plug-in loading, optional plug-in information, and plug-in properties. This information appears in a new text file after the IDE starts up. The text file also includes a complete list of installed plug-ins and their associated preference panels, compilers, and linkers.

You can save the text file, print it, and use it as an error reference for troubleshooting your plug-ins. The text file provides suggestions for correcting general plug-in errors.

Enable this checkbox to disable all third-party Common Object Model (COM) plug-ins for the IDE. This option is useful for troubleshooting problems with the IDE.

The Shielded Folders preference panel, shown in Figure 8.9, allows you to configure the IDE to ignore folders during certain operations. You specify regular expressions that match the names of the folders that you wish to ignore. The IDE treats matching folders as shielded folders and ignores their contents. For more information about regular expressions, see "Using Regular Expressions (grep)".

The Shielded Folders list at the top of the panel shows the current list of regular expressions. The IDE uses this list to determine whether to shield folders from the current project. The following regular expressions appear in the Shielded Folders list by default:

• The \(.*\) regular expression matches folders with names that begin and end with parentheses, such as (Project Stationery).
• The CVS regular expression matches folders named CVS. With this regular expression, the IDE skips data files used by the CVS version control system.
• The .*[_]Data regular expression matches the names of folders used by the IDE to store target data information, such as MyProject_Data.
Shielded Folders Preference Panel:

A bullet in the Project operations column, whose label appears at left, indicates that the IDE ignores matching folders for project operations. Such operations include dragging a folder into the Project window, building a project, or searching access paths after choosing the Open command.

A bullet in the Find-and-compare operations column, whose label appears at left, indicates that the IDE ignores matching folders for find-and-compare operations. Such operations include dragging a folder into fields in the Find window, or comparing folder contents.

To add a regular expression to the Shielded Folders list, follow these steps:

1. Enter in the Regular Expression field the expression that specifies the folders you wish to ignore.

You can enter the name of a specific folder, or you can enter a regular expression that matches several folder names.

2. Choose whether to shield matching folders from project operations, from find-and-compare operations, or from both.

Enable the Project operations checkbox, the Find and compare operations checkbox, or both. During the operations that you specify, the IDE ignores folders with names that match the regular expression.

3. Click Add.

After you click the Add button, the regular expression appears in the Shielded Folders list. Bullets in the list indicate the operations for which the IDE ignores matching folders.

4. Click Save.

To modify an existing regular expression, follow these steps:

1. Select the regular expression that you wish to modify.

2. Modify the regular expression.

If desired, enter a new regular expression in the Regular Expression field.

3. Modify the operations for which to shield matching folders.

Enable the Project operations checkbox and the Find and compare operations checkbox as desired.

4. Click Change.

After you click the Change button, the modified regular expression appears in the Shielded Folders list. Bullets in the list reflect the changes that you made to the corresponding operations.

5. Click Save.

To delete an existing regular expression, follow these steps:

1. Select the regular expression that you wish to delete.

2. Click Remove.

After you click the Remove button, the IDE deletes the regular expression from the Shielded Folders list.

3. Click Save.

The Source Trees preference panel, shown in Figure 8.10, lets you define global source trees (root paths) for use in your projects. You can define access paths and build-target output in terms of source trees. Using this approach, you can share projects across various hosts. You need only make minor changes to the source-tree paths to maintain project functionality.

You can use the source trees that you define in the IDE Preferences window for all projects. However, you can use the source trees defined in the Target Settings window only for the current build target in the active project. If you define the same source trees in both windows, the target-specific source trees take precedence over the global source trees. For more information about the target-specific version of the Source Trees panel, see "Source Trees".

This list shows all source trees defined for use with the IDE. The list contains two columns:

• Name-This column shows the name that you assign to each source tree. After you define a source tree, you can use the source-tree name in subsequent access-path definitions. For more information, see "Add".
• Path-This column shows the path that you defined for each source tree. After transferring your project to a new host, you might need to modify the source-tree paths. Your modifications automatically propagate to all access paths defined in terms of the source trees. See "Change" for more information about modifying the current path.

Use this field to enter a name for a new source tree, or to change the name of an existing source tree.

Use this pop-up menu to choose one of the following types of source trees:

• Absolute Path-This type of source tree is based on a file path.
• Environment Variable-This type of source tree is based on an existing environment variable definition. You cannot create or modify this type of source tree on the Mac OS-hosted IDE.
• Registry Key-(Windows) This type of source tree is based on an existing registry key entry.

To add a new source tree, follow these steps:

1. Select the appropriate source-tree type from the Type pop-up menu.

See "Source-Tree path types" for more information about the path types listed in the pop-up menu.

2. Enter a name for the new source tree in the Name field.

3. Click Choose to select the path that you want the source tree to represent.

Use the dialog box, shown in Figure 8.11 (Windows), Figure 8.12 (Mac OS), and Figure 8.13 (Solaris and Linux), to select the path.

4. Click Add to add the new source tree to the Source Trees list.

Repeat these steps until you finish adding source trees, then click Save. You can then define access paths in terms of the source trees.

You can choose at least one of the following path types when defining a source tree:

• Absolute Path-This path type defines a path from the root level of the startup hard drive to the folder whose path you wish to add, including all folders in between. You must update an absolute path when the name of any item along the path changes, such as after moving the project to a new location.
• Compiler Relative-This path type defines a path from the folder that contains the CodeWarrior IDE to the folder whose path you wish to add. You do not need to update compiler-relative paths after you move a project, as long as the hierarchy of the relative path stays the same. You cannot create a relative path to a folder on a different hard drive than where the CodeWarrior IDE resides.
Source-Tree Path Selection Dialog Box (Mac OS):

• System Relative-This path type defines a path from the base folder of the operating system to the folder whose path you wish to add. You do not need to update system-relative paths after you move a project, as long as the hierarchy of the relative path stays the same. You cannot create a relative path to a folder on a different hard drive than where the base folder of the operating system resides.

Choosing the Environment Variable or Registry Key source-tree types enables the field shown in Figure 8.14. Enter in this field the path to the environment variable or registry key.

Saved source trees appear in path pop-up menus for your project. For example, Figure 8.15 shows how you can define an access path in terms of a source tree named Sample. You can also define the target output for your project in terms of the source trees by using the Output Directory field in the Target Settings panel. For more information about this settings panel, see "Target Settings".

To modify an existing source tree, follow these steps:

1. Select the source-tree name in the Source Trees list.

2. Modify the name and type of the source tree as desired.

Enter a new name for the source tree in the Name field, and choose a new source-tree type from the Type field.

3. Click Change.

Your modifications appear in the Source Trees list.

Repeat these steps until you finish modifying source trees, then click Save. You can then define access paths in terms of the modified source trees.

To remove an existing source tree, follow these steps:

1. Select the source-tree name in the Source Trees list.

2. Click Remove.

The IDE deletes the selected source tree from the Source Trees list.

Repeat these steps until you finish deleting source trees, then click Save to commit your changes.