Module Menu

The commands on this menu let you specify lines of code that are inserted into the primary module of generated code at specified points. Unlike code preludes, which are attached to individual widgets, module preludes and headings apply to the whole module.

Loose Bindings - Displays the Loose Bindings dialog, allowing you to set loose resource bindings for the application in general.

Module Preludes - Displays a dialog box that lets you enter lines of code to be entered at or near the beginning of the generated code file. The Module Heading is inserted at the beginning of the primary code module and at the beginning of the stubs file, if generated. The Module Heading is typically used for SCCS ids, versions and other identifying information.

The Module Prelude is inserted after the generated X-Designer #include directives, if any, and is typically used for #include or #define directives or extern declarations required by your code preludes.

The Resource Prelude is inserted after the X-Designer generated comment in the X resource file. It can be used to set global application resources or to #include another resource file.

Help Defaults - Displays a dialog which allows you to specify defaults for the help system.

X-Procedures - Follow the link below to discover how:

can be added to your design and when you should use them.

Xrm Options - Displays the Xrm Options dialog, which is used to refine the way in which application arguments are parsed by the routines which initialize the X system.

Groups... - This item opens the "Group Editor" where you can manipulate the contents and access of the groups and their components.

X Errors Dialog - Displays a dialog where application error and message handlers can be specified.

Visuals Dialog - Displays a dialog where Colormap and preferred Visual Class data can be specified for the application.

Microsoft Windows compliant - This toggle (only present when X-Designer is in Microsoft Windows mode) is used to indicate that the design is Microsoft Windows compliant; that is, it is possible to generate MFC code for it. The toggle is set to indicate that the design is compliant. If the design becomes non-compliant, because an old design is read in or by means of cut and paste, the toggle is unset and the Microsoft Windows Compliance Failure dialog is displayed. This toggle can be reproduced on the toolbar.

Application class - The MFC and Motif XP flavors use an instance of the CWinApp class to represent the application. By popping up the Application class dialog you can change the base class name, the class name and the instantiate as name for this instance. This item is only present when X-Designer is in Microsoft Windows mode.

See also: