# 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 WorkShop Visual #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 WorkShop Visual 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.

The Default Path field denotes the path used for help document names. It is also used in WorkShop Visual as a fallback location for generated code.

The Default Document field is used if a marker for help is set but no document is specified for the widget or any of the widget ancestors.

The Path Resource and Path environment variable fields allow you to provide a dynamic Help document context: code will be generated so that any values specified will be used to override any setting of the Default path: the runtime environment variable takes precedence over the static resource setting.

The Default Translation field will cause a translation to be added to every widget which has a help marker; the associated Action for this translation will always be Help. For example, a translation `CtrlA' will mean that unless specified otherwise Control A will cause the Help message window to be displayed for a widget which has a help marker.

The `Always own window' toggle, when set, causes code to be generated so that each access to the Help System will result in a new Help Document window.

Microsoft Windows compliant - This toggle (only present when WorkShop Visual 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 WorkShop Visual is in Microsoft Windows mode.

See also:

- Module Prelude dialog
- Loose Bindings
- Help Defaults dialog
- Microsoft Windows mode
- Microsoft Windows compliance
- Application class dialog
- About WorkShop Visual