Browser Options Menu

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: Displays a warning dialog with the message "This will save the file setting(s) to the BX application resources." Click OK to continue, Cancel to cancel.

---

Directory Path

The Directory Path field allows you to specify the directory into which generated files will be written.

---

Note: Changing the directory here changes the directory throughout Builder Xcessory. Builder Xcessory uses only one directory at a time.

---

File Output Names

The File Output Names field specifies the following files (defaults are in parentheses):

· Imakefile (Imakefile) is the imakefile that specifies C++ imake information.

· Makefile (makefile-C) is the C++ makefile.

· Class Tree Root (UIComponent) contains the root class from which all classes created in Builder Xcessory are derived.

· Main (main-C.C) initializes the Motif toolkit and creates your application's shell widgets and classes. Changing this allows you to use a different base class for your application components. Builder Xcessory creates an unrealized applicationShell and creates all topLevelShell children for all top-level windows. To modify the main-C.C file for your application, make your changes in the user code blocks. Any changes made outside the user code blocks will be overwritten in subsequent generations. To write your own main routine, disable subsequent file generation by unsetting the toggle.

· Constants (defs-C.h) contains pixmaps, declarations of constants, and global instances of widgets or classes used in the interface.

· Utilities (bxutils-C.C) contains convert functions.

· Callbacks (callbacks-C) contains any callback information for non-class widgets.

· App Defaults (app-defaults) is the file that includes all resources with app-defaults value set to App. The user can change an app-default resource value by editing the app-defaults resource file, overriding the file from a local resource file, or entering the toolkit option -xrm on the command line.

File Extensions

The File Extensions field specifies the following file extensions:

· C++ Source Extension contains the value appended to the source file name after a dot. The default is C.

· C++ Header Extension contains the value appended to the header file after a dot. The default is h.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: Displays a warning dialog with the message "This will save the code setting(s) to the BX application resources." Click OK to continue, Cancel to cancel.

---

Application Class

The Application Class resource field allows you to enter a class name for the application. Xt uses the Application Class name to find and load application resources, and the application defaults file. When you install your application, the app-default file name should be the same as the application class name.

Application Name

The Application Name resource field allows you to assign a name to your current application. Xt uses the Application Name to resolve precedence of resource specifications.

Toggle options

You can set the following toggle options:

· User-Specified Main Loop specifies a function to call rather than XtAppMainLoop.

· Initialize Localization Support supports whether or not to generate a call to XtSetLanguageProc in the application initialization. Calling this function enables support in X and Motif for non-English locales.

· Generate Derived Files generates an additional subclass for each user-defined class. If set, all application code must be written in the derived file. Default name is "class name"Derived.C.

· (Parented) Dialog Shell Initially Unmanaged toggles to manage Dialog Shells, such as XmDialogShell, in the main-C.C file.

· Use Old Style Constructor for backward compatibility. In previous versions of Builder Xcessory, constructors for user-defined classes created the interface, and the parent widget ID was passed as a parameter.

· Remove Overridden Exposed Callbacks removes the class callbacks when overridden. Otherwise both methods will be called.

· Don't Create Unmanaged Windows delays creation of unmanaged windows.

· Ignore Geometry Resources on Shells does not print shell geometry (x, y, width, height) in the output code.

· Delete Nested Classes in Destructor deletes nested classes created with a New operation inside the create method in the destructor.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: A warning dialog with the message "This will save the include setting(s) to the BX application resources." is displayed. Click OK to continue, Cancel to cancel.

---

C++ Output Include Information

Any headers or comments you enter in the C++ Output Include Information text field are included at the head of each file generated, under the commented heading User Supplied Include Files.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: A warning dialog with the message "This will save the make setting(s) to the BX application resources." is displayed. Click OK to continue, Cancel to cancel.

---

Make Target

Name of the target of the make executed when Make Application is selected from the Browser Project menu (default is main-C).

CC

Name of the C++ compiler.

CFLAGS

C++ compiler flags.

LIBS

X, Motif, and any other widget libraries.

Toggle option

Setting the toggle option Don't Include Ungenerated Class Files excludes classes for which you disabled code generation (see Generate Class ) from the list of source and object files that comprise your application. This is useful if you collected classes into a library, and want to link your application with this library.

Makefile Information

Include additional Makefile comments and information in this text area.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: A warning dialog with the message "This will save the file setting(s) to the BX application resources." is displayed. Click OK to continue, Cancel to cancel.

---

Directory Path

The Directory Path field allows you to specify the directory into which generated files will be written.

---

Note: Changing the directory here changes the directory throughout Builder Xcessory. Builder Xcessory uses only one directory at a time.

---

File Output Names

The File Output Names field specifies the following files:

· Imakefile (Imakefile)

Imakefile that specifies ViewKit imake information.

· Makefile (makefile-vk)

ViewKit makefile for the current platform.

· Main (main-vk)

Initializes the application and instantiates the Window components.

· Constants (defs-vk)

Contains any pixmaps, declarations of constants used in the interface.

· Utilities (bxutils-vk)

Contains convert functions.

· Callbacks (callbacks-vk)

Contains any callback information for non-class objects.

· App Defaults (app-defaults)

File that includes all resources with app-defaults value set to App. The user can change an app-default resource value by editing the app-defaults resource file, overriding the file from a local resource file, or entering the toolkit.

File Extensions

The File Extensions field specifies the following file extensions:

· ViewKit Source Extension contains the value appended to the ViewKit source file name after a dot. The default is C.

· ViewKit Header Extension contains the value appended to the ViewKit header file after a dot. The default is h.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: A warning dialog with the message "This will save the app setting(s) to the BX application resources." is displayed. Click OK to continue, Cancel to cancel.

---

Application Class

The Application Class resource field allows you to enter a class name for the application. Xt uses the Application Class name to find and load application resources, and the application defaults file When you install your application, the app-default file name should be the same as the application class name.

Application Name

The Application Name resource field allows you to assign a name to your current application. Xt uses the Application Name to resolve precedence of resource specifications .

Toggle options

You can set the toggles for the following options:

· Custom Event Processing allows you to specify that name of a function to pass to VkApp::run(). ViewKit will call this function for every X event received. Builder Xcessory will also generate a stub for this function in main-vk.C .

· UseVkApp Subclass allows you to specify a subclass of VkApp to use in main-vk.C .

VkApp Subclass Include

Allows you to specify the include file for the VkApp subclass specified when you set the UseVkApp Subclass toggle

Toggle options

You can set the following toggle options:

· Remove Overridden Exposed Callbacks removes the class callbacks when overridden. Otherwise both methods will be called.

· Delete Nested Classes in Destructor deletes nested classes created with a New operation inside the create method in the destructor.

---

Note: The create method must be called to avoid causing an error.

---

· Initialize Fallback Resources inserts code and a user code block in main-vk.C where you can insert you application's fallback errors.

· (Parented) Dialog Shell Initially Unmanaged toggles whether dialogs initially should be hidden regardless of their state in Builder Xcessory.

· Use VkRunOnce allows you to specify that only one single instance of an application can be run on any system at any one time. Also allows you to pass arguments to the running version of the application. Selecting this option will cause an instance of VkRunOne2 to be created in main-vk.C .

· UseToolTalk uses VkMsgApp (instead of VkApp) which sets up a ToolTalk session. All windows are subclassed from the VkMsgWindow instead of VkWindow, and VkMsgComponent is used instead of VkComponent. In cases where you specify your own subclasses of VkApp or VkComponent, the generated code assumes they are subclasses of VkMsgApp or VkMsgComponent, respectively.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: Displays a warning dialog with the message "This will save the app setting(s) to the BX application resources." Click OK to continue, Cancel to cancel.

---

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: A warning dialog with the message "This will save the make setting(s) to the BX application resources." is displayed. Click OK to continue, Cancel to cancel.

---

ViewKit Output Include Information

Any headers or comments you enter in the ViewKit Output Include Information text field are included at the head of each file generated, under the commented heading User Supplied Include Files.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: A warning dialog with the message "This will save the make setting(s) to the BX application resources." is displayed. Click OK to continue, Cancel to cancel.

---

Make Target

Name for the command make executed when Make Application is selected from the Browser Project menu. Default is main-vk.

CC

Name of the C++ compiler.

CFLAGS

C++ compiler flags.

LIBS

X, Motif, ViewKit and any other widget libraries.

Toggle option

Setting the toggle option Don't Include Ungenerated Class Files causes all classes for which you chose not to generate code to be excluded from the makefile with the assumption that they are part of a library listed in the LIBS section.

Makefile Information

Include additional Makefile comments and information in this text area.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: Displays a warning dialog with the message "This will save the file setting(s) to the BX application resources." Click OK to continue, Cancel to cancel.

---

Directory Path

The Directory Path field allows you to specify the directory into which generated files will be written.

---

Note: Changing the directory here changes the directory throughout Builder Xcessory. Builder Xcessory uses only one directory at a time.

---

File Output Names

The File Output Names field specifies the following files:

· Imakefile ( Imakefile )

Imakefile that specifies C imake information.

· Makefile ( makefile-c )

C makefile for the current platform.

· Main ( main-c.c )

Initializes the toolkit and calls the Widget Creation routine.

· Creation ( creation-c.c )

Contains code to create the widget hierarchy. The functions in this file are called by the Main file.

· Callbacks ( callbacks-c.c )

Contains any callback stubs for any callbacks defined in Builder Xcessory. When you write the Callbacks file to a directory with an existing file of the same name, Builder Xcessory scans the existing file for the names of functions and appends callback stubs for undefined callbacks only. Callbacks are never removed from this file or overwritten. Stubs for timers, event handlers, and work procedures are also output in this file.

· Constants ( creation-c.h )

Contains any pixmaps, declarations of constants, and global instances of widgets or classes used in the interface.

· Utilities ( bxutil-c.c )

Contains convert functions, predefined callback code, and the necessary xpm functions.

· App Defaults (app-defaults)

Includes all resources with app-defaults value set to App. The user can change an app-default resource value by editing the app-defaults resource file, overriding the file from a local resource file, or entering the toolkit.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: A warning dialog with the message "This will save the code setting(s) to the BX application resources." is displayed. Click OK to continue, Cancel to cancel.

---

Application Class

The Application Class resource field allows you to enter a class name for the application. Xt uses the Application Class name to find and load application resources, and the application defaults file.

Application Name

The Application Name resource field allows you to assign a name to your current application. Xt uses the Application Name to resolve precedence of resource specifications .

Toggle options

You can set the following options:

· User-Specified Main Loop specifies a function to call in place of the call to XtAppMainLoop.

· Generate ANSI C

When unset, Builder Xcessory generates standard K&R C code. When set, generates ANSI C. Set by default.

· Initialize Localization Support supports whether or not to generate a call to XtSetLanguageProc in the application initialization. Calling this function enables support in X and Motif for non-English locales.

· (Parented) Dialog Shell Initially Unmanaged toggles to manage Dialog Shells, such as XmDialogShell, in the main-c.c file.

· Put (Unparented) Dialog Shells in Creation Routines generates code to create the XmDialogShell in the creation-c.c file when a dialog shell that is the child of the root is encountered.

· Reverse Order of (Parented) Dialog Shells reverses the order of Dialog Shells that were not children of the root.

· Remove Overridden Exposed Callbacks removes the class callbacks when overridden. Otherwise both methods will be called.

· Don't Create Unmanaged Windows delays creation of unmanaged windows.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: Displays a warning dialog with the message "This will save the include setting(s) to the BX application resources." Click OK to continue, Cancel to cancel.

---

C Output Include Information

Any headers or comments you enter in the C Output Include Information text field are included at the head of each file generated, under the commented heading User Supplied Include Files.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: Displays a warning dialog with the message "This will save the make setting(s) to the BX application resources." Click OK to continue, Cancel to cancel.

---

Make Target

Name of the target of the make executed when Make Application is selected from the Browser Project menu (default is main-c).

CC

Name of the C compiler.

CFLAGS

C compiler flags.

LIBS

X, Motif, and any other widget libraries.

Toggle option

Setting the toggle option Don't Include Ungenerated Class Files excludes classes for which you disabled code generation (see Generate Class ) from the list of source and object files that comprise your application. This is useful if you collected classes into a library, and want to link your application with this library.

Makefile Information

Include additional Makefile comments and information in this text area.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: A warning dialog with the message "This will save the file setting(s) to the BX application resources." is displayed. Click OK to continue, Cancel to cancel.

---

Directory Path

The Directory Path field allows you to specify the directory into which generated files will be written.

---

Note: Changing the directory here changes the directory throughout Builder Xcessory. Builder Xcessory uses only one directory at a time.

---

File Output Names

The File Output Names field specifies the following files:

· Imakefile ( Imakefile )

Imakefile that specifies both UIL and C imake information.

· Makefile ( makefile-uil )

Makefile for the current platform. Has targets for UIL as well as the associated C files.

· Main ( main-uil.c )

Initializes the toolkit, initializes Mrm, and makes Mrm calls in order to create widgets. Although this file is intended as a template to enable you to immediately compile the interface output from Builder Xcessory, it will not be adequate for all applications. In particular, Builder Xcessory creates an unrealized applicationShell and creates all topLevelShell children for all top-level windows, as recommended in Asente, Converse, and Swick's X Window System Toolkit.

---

Note: You can modify this file within the specified user code blocks, but changes made outside these blocks will not be preserved between code generation sessions.

---

· UIL File ( uil.uil )

Contains a description of the widgets. Compiled to a .uid file which is then read by the Mrm calls at run-time to create the widgets. Builder Xcessory generates a backup file whenever it overwrites an existing UIL file. Automatic backup is provided for the default filename uil.uil or any customized filename. If, for example, you write the renamed UIL file new_uil.uil, and a copy of this file already exists, Builder Xcessory generates the backup file new_uil.uil~. These UIL files are identical to the files generated when you select Save from the Browser File menu.

· Callbacks (callbacks-uil.c)

Contains callback stubs. When you write out the Callbacks file to a directory with an existing file of the same name, Builder Xcessory scans the existing file for the names of functions and appends callback stubs for undefined callbacks only. Callbacks are never removed from this file and are never overwritten. Stubs for timers, event handlers, and work procedures are also output in this file.

· Constants (main-uil.h)

Contains declarations of constants, and global instances of widgets or classes used in the interface.

· Utilities (bxutil-uil.c)

Contains convert functions and predefined callback code.

· App Defaults (app-defaults)

File that includes all resources with app-defaults value set to App. The user can change an app-default resource value by editing the app-defaults resource file, overriding the file from a local resource file, or entering the toolkit

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: A warning dialog with the message "This will save the app setting(s) to the BX application resources." is displayed. Click OK to continue, Cancel to cancel.

---

Application Class

The Application Class resource field allows you to enter a class name for the application. Xt uses the Application Class name to find and load application resources, and the application defaults file.

Application Name

The Application Name resource field allows you to assign a name to your current application. Xt uses the Application Name to resolve precedence of resource specifications .

Toggle options

You can set the following options:

· User-Specified Main Loop specifies a main loop to replace XtAppMainLoop.

· Generate ANSI C

When unset, Builder Xcessory generates standard K&R C code. When set, generates ANSI C. Set by default.

· Don't Create Unmanaged Windows delays creation of unmanaged windows.

· Ignore Geometry Resources on Shells does not print shell geometry
(x, y, width, height) in the output code.

C Output Include Information

Any headers or comments you enter in the C Output Include Information text field are included at the head of each file generated, under the heading User Supplied Include Files.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: Displays a warning dialog with the message "This will save the include setting(s) to the BX application resources." Click OK to continue, Cancel to cancel.

---

Make Target

Make Target (main-uil) is the name of the target of the make command executed when you select Make Application from the Browser Project menu.

CC

Name of the C compiler.

CFLAGS

C compiler flags.

LIBS

X, Motif, and any other widget libraries.

Makefile Information

Include additional Makefile comments and information in this text area.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: Displays a warning dialog with the message "This will save the file setting(s) to the BX application resources." Click OK to continue, Cancel to cancel.

---

Directory Path

Allows you to specify the directory into which to write generated files.

---

Note: Changing the directory here changes the directory throughout Builder Xcessory (Builder Xcessory uses only one directory at a time).

---

File Output Names

The File Output Names field specifies the following files:

· Makefile (makefile-java)

Java makefile for current platform.

· Main (MainApp)

Main file which instantiates all top level objects,

---

Note: If you have only one top level object, you can deselect the Main toggle on the File Names tab of the Generation Preferences dialog.

---

· HTML (MainApp)

HTML file for the MainApp Class that allows the application to run in a browser or an applet viewer.

· Constants (Def)

Contains any pixmaps, declarations of constants, and global instances of objects or classes used in the interface.

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: Displays a warning dialog with the message "This will save the app setting(s) to the BX application resources." Click OK to continue, Cancel to cancel.

---

Toggle options

You can set the following toggle options:

· Make Main File An Applet

Makes the main class into an applet rather than an application.

· Applets Implement Runnable toggles whether generated applets will implement the runnable interface for threading. All applets or subclasses of applets will Implement Runnable. Off by default.

· Generate HTML files for all valid classes

Creates an HTML file for all classes created in Builder Xcessory, which can be run in a browser or applet viewer.

· Dialog Shells Initially Unmanaged

Toggles to manage Dialog Shells in the MainApp file.

---

Note: Only classes derived from Applets, Frames, or Dialogs can be run in a browser or Applet viewer.

---

Java Makefile

Click on the Makefile tab to display the Makefile Menu of the Java Generation Preferences dialog:

Save As Default

Saves the specified settings on this menu as the default settings. The settings are saved to the .bxrc file and appear when you perform a New operation or when you restart Builder Xcessory.

---

Note: A warning dialog with the message "This will save the make setting(s) to the BX application resources." is displayed. Click OK to continue, Cancel to cancel.

---

Compiler Flags

Compiler flags. Builder Xcessory default is -verbose.

Toggle option

Setting the toggle option Don't Include Ungenerated Class Files excludes classes for which you disabled code generation (see Generate Class ) from the list of source and object files that comprise your application. This is useful if you collected classes into a library, and want to link your application with this library.

Makefile Information

Include additional Makefile comments and information in this text area.

Grid Units

Allows you to change the placement grid dimensions. Enter the width of a grid square in pixels in the Grid Units text field. Default value is 10.

Motif Version

Allows you to specify the version of Motif. Default value is 1.2.

Panner Timeout

Allows you to specify the speed (in milliseconds) of the automatic panning of the Browser display. Default value is 1000.

Autosave Interval

Allows you to specify the interval, in button and key actions, between automatic backups of the UIL file. Default value is 100.

Toolbars options

Controls the display of both the Browser and the Resource Editor Toolbars. You can set the following toggle options:

· Icons and Labels

· Icons Only

· Labels Only

Behavior toggle options

You can set the following toggle options:

· Save Window State on Exit

Saves the size, position, and icon state of Builder Xcessory windows between sessions. When set, the window state of your current Builder Xcessory session will be used the next time you start Builder Xcessory.

· Auto Dismiss Startup Panel

Dismisses the ICS Window after Builder Xcessory finishes loading. Unset by default.

· Confirm Delete Actions

When set, all deletions must be confirmed by the user. Set by default.

· Auto Menu Popup

When set, the children of a menu are displayed on the interface when you click on the menu parent, and when you create a menu. Set by default.

· Strict Dialogs

According to the OSF/Motif Style Guide, only those objects which inherit from the XmBulletinBoard widget class may be children of an XmDialogShell. When Strict Dialogs is set, Builder Xcessory complies with that recommendation. When Strict Dialogs is unset, Builder Xcessory permits you to create any object as the child of an XmDialog Shell. Set by default.

---

Note: This option is not available for Java.

---

· Delay Shell Realize

Unset by default. When set, each top level shell of an interface read into or opened by Builder Xcessory is initially deselected in the Browser list, and the widget tree is not realized until the top level shell is selected. This feature allows you to read or open very large interfaces more efficiently.

· Tree Initially Closed

When unset, the descendants of an object created along with that object are displayed on the Browser object instance hierarchy. The top level shell or parent's folder defaults to Open. When Tree Initially Closed is set, the descendants of an object created along with that widget are hidden on the Browser object instance hierarchy. (The top level shell or parent's folder defaults to Closed.) Unset by default.

· Center Browser Tree

When set, the object instance hierarchy display on the Browser is automatically centered around the currently selected object. Unset by default.

· Raise Resource Editor

When unset, the Resource Editor remains where it is on your display (even iconified) when you double-click on an object to update the Resource Editor. When set, the Resource Editor is raised to the top of your display (and deiconified as necessary) when you double-click on an object to update the Resource Editor. Unset by default.

· Single Class View

When set, shows only one class at a time. Clicking on another class in the list hides the current class and shows the new class. Useful for browsing large collections of classes. Unset by default.

· Start with EPak Widgets

When set, the Palette includes the members of the ICS Motif EnhancementPak on startup. Unset by default in Builder Xcessory. Set by default in BX PRO.

Save File toggle options

You can set the following toggle options:

· Always Generate Pixmaps generates code for any pixmaps loaded into Builder Xcessory, even if unused. Typically, Builder Xcessory will generate only code for pixmaps used in the application. Unset by default.

· Generate Special UIL

When set, Builder Xcessory outputs user-defined widgets to compile with the standard UIL compiler (without rebuilding). Unset by default.

---

Note: This option is not applicable in Java.

---

· Xt Name Compliant

When unset, allows instance names of widgets to begin with an upper case letter. When set, forces a lowercase letter. Capitalized widget names might cause problems with the proper inheritance of application defaults resource values and conflicts with Xt specifications. Set by default.

Button One Shell

This menu allows you to select the kind of shell created when you drag and drop an object from the Palette with MB1. The shell options on the scroll menu include the following:

· ApplicationShell

· TopLevelShell

· XmDialogShell

· TransientShell

Default value is TopLevelShell.

---

Note: These menu options are not applicable in Java.

---

Button Three Shell

This menu allows you to select which kind of shell is created when you drag and drop an object from the Palette with MB3. The shell options on the scroll menu include the following:

· ApplicationShell

· TopLevelShell

· XmDialogShell

· TransientShell

Default value is XmDialogShell.

---

Note: These menu options are not applicable in Java.

---

Scroll menu options

If your environment does not have a source code control system, or you want to use another system, select one of the following options:

· Unset

Completely disables the use of source code control within Builder Xcessory. The Check Out and Check In options in the File menu become insensitive, and Builder Xcessory does not query whether a file should be checked out.

---

Note: If your development environment supports integration with its source code control tool, this option might be listed as an option to use your environment's source code control tool.

---

· Use RCS

F ills the text fields below the option menu with the default RCS commands for locking a file, checking out a file, cancelling a check out, and checking in a file. You can edit any of these text fields.

· Use SCCS

Fills the text fields below the option menu with the default SCCS commands for checking out and locking a file, checking out a file, cancelling a check out, and checking in a file. You can edit any of these text fields.

· Use ClearCase

Fills the text fields below the option menu with the default ClearCase commands for checking out and locking a file, checking out a file, cancelling a check out, and checking in a file. You can edit any of these text fields.

· User Specified

Clears the text fields. You must supply command strings for each field. If you do not enter a command string in a field, its associated action will not be available through the Check Out and Check In dialogs.

Source Code Control text fields

The following text fields are available on the Source Code Control menu (defaults depend on whether you selected RCS, SCCS, Clear Case or User Specified):

· Check Out Locked Command

Checks file out from source code control system, makes the file editable, and locks it.

· Check Out Unlocked Command

Gets a read-only version of the most recent version of the file.

· Cancel Check Out Command

Cancels a check-out command. Any changes you make to the checked-out file are ignored. The original file remains intact and checked in.

· Check In Command

Checks the edited file back in.

· Header Keywords

Revision control for RCS, SCCS, Clear Case or User Specified. Allows you to insert identification keywords in Builder Xcessory .uil file. The default for RCS is $ID$. The default for SCCS is %W% %D% %T%. The other tools default to blank. Consult the appropriate source code control documentation for more information.

Options syntax in Builder Xcessory

Builder Xcessory executes many of the source code control commands by constructing a command as it would be entered at a shell prompt. The command lines for the various commands use symbolic representations for the various user-specified command line options.

Builder Xcessory substitutes the appropriate value for the representation when it builds the command line. In general, the options syntax is as follows:

%option_name[actual_option_flag]

Everything within the brackets "[ ]" is substituted for the option name in the command line. Most options may also include "%s" within the brackets "[ ]", indicating where to insert dynamically determined text, (such as a file name or a line number).

Example

For example, assume a command to check out a file from source code control was "checkout" and it takes the name of the file to check out as an argument. The following is entered:

checkout %file[%s]

If the filename argument must follow the flag "-f", the command is entered as follows:

checkout %file[-f%s]

---

Note: Items outside an option description, that is, not within the brackets "[ ]", are added verbatim in the command line.

---

Command line option substitutions

The following list describes the command line option substitutions available for source code control commands:

---

Note: None of these options are required.

---

· %file

Indicates the filename for the source code control operation. You can use %s within the brackets "[ ]".

· %version

Specifies file version string. You can use %s within the brackets "[ ]".

· %comments

Specifies any comments to be associated with a particular revision of a file. You can use %s within the brackets "[ ]".

· %overwrite

Boolean flag used for checking out files. If True, the contents of the brackets "[ ]" are substituted on the command line. If False, nothing is added.

· %keep

Boolean flag used when checking in files. If True, the contents of the brackets "[ ]" are substituted on the command line. If False, nothing is added.

Scroll menu options

The Debugger & Build Manager menu allows you to select your debugger, as follows:

· Use Environment Tools

Use your environment's debugger. If you start Builder Xcessory from within your development environment, the debugger option allows you to choose this option.

· Use CenterLine Tools

Use CenterLine's debugger. Choose this option if you use either CodeCenter or ObjectCenter for application development and debugging.

---

Note: The selected debugger becomes the default in your next Builder Xcessory session. For example, if you start Builder Xcessory from within your environment and select Use Environment Tools, the default debugger option is Use Environment Tools when you start your next Builder Xcessory session from within your environment. If you start Builder Xcessory outside your environment (on the command line), the Use Environment option becomes the Unset option.

---

· Unset

Unsets the debugger option.

· Execute CenterLine Command toggle

Instructs Builder Xcessory to try to start the selected CenterLine debugger. This toggle button is insensitive unless you choose Use CenterLine Tools. If unset, Builder Xcessory assumes that the Centerline debugger is already running and tries to connect.

CenterLine Options

You can set the following Centerline options:

· C++ Message

Commands to send to CenterLine to start a debug session on C++ code.

· C Message

Commands to send to CenterLine to start a debug session on C code.

· Reset Message

Commands sent when Builder Xcessory switches from Debug Mode to Build or Play Mode.

· C++ Command

Command used to start CenterLine debugger if necessary. The default is objectcenter-motif. This command is used with C++ code.

· C Command

Command used to start CenterLine debugger if necessary. The default is xcodecenter. This command is used with C code.

Options syntax in Builder Xcessory

Builder Xcessory executes the text editor commands by constructing a command as it would be entered at a shell prompt. The command lines for the various commands use symbolic representations for the various user-specified command line options.

Builder Xcessory substitutes the appropriate value for the representation when it builds the command line. In general, the options syntax is as follows:

%option_name[actual_option_flag]

Everything within the brackets "[ ]" is substituted for the option name in the command line. Most options may also include "%s" within the brackets "[ ]", indicating where to insert dynamically determined text, (such as a file name or a line number).

Example

For example, assume a command to edit a file was "editor" and it takes the name of the file to edit as an argument. This is entered as the following:

editor %file[%s]

If the filename argument must follow the flag "-f", the command is entered as

editor %file[-f %s]

Command line option substitutions

The following list describes the command line option substitutions available for text editor commands:

· %line

Specifies the line of the specified file to go to when the file is opened. %s indicates the line number to which to move the cursor.

· %file

Specifies the name of the file to open. %s indicates the position of the filename.

XRunner Library

Setting the XRunner Library toggle specifies the library that your application is linked to for XRunner to communicate with the application.

When you compile, append xrunner to the standard make command, as follows:

make -f <makefile> xrunner

When using Imakefiles generated by Builder Xcessory, enter make xrunner (uses the last generated Makefile):

When the toggle is set, XRunner targets are added to makefile, so that the XRunner libraries are built into the executable. When you run XRunner outside of Builder Xcessory, XRunner will query your application according to this setting.

---

Note: XRunner integration is supported for versions of XRunner up to and including 2.0.

---

Purify Command

Setting Purify Command specifies the command which Builder Xcessory places in front of the compile line in the generated C or C++ Makefile for the application. When you compile, append pure to the standard make command, as follows:

make -f <makefile> pure

For the correct Imakefile enter make pure (uses the most recent Makefile generated from the Imakefile):

When the toggle is set, the "pure" targets is added to makefile, so that the Purify commands are built into the executable. The application validates memory use and reports when a memory violation occurs. Purify will also report any leaked memory.

MemAdvisor

Setting MemAdvisor Command specifies the command which Builder Xcessory places in front of the compile line in the generated C or C++ Makefile for the application. When you compile, append pure to the standard make command, as follows:

make -f <makefile> pure

For the correct Imakefile enter make pure (uses the most recent Makefile generated by Imakefile):

When the toggle is set, MemAdvisor targets are added to makefile, so that the MemAdvisor commands are built into the executable. The application validates memory use and reports when a memory violation occurs. MemAdvisor will also report any leaked memory.

Look and Feel

Set the converter to produce either Motif or OpenLook appearance and behavior. Set to Motif by default.

Reposition

When set to Yes, the converter will attempt to reposition objects where appropriate. When set to No, reposition is not attempted. Set to Yes by default.